Changelog

3.13.0 (2022-11-21)

3.12.7 (2022-10-11)

3.12.6 (2022-07-25)

3.12.4 (2022-06-13)

3.12.3 (2022-06-01)

3.12.2 (2022-03-28)

3.12.1 (2022-02-15)

3.12.0 (2022-02-02)

{% hint style=“warning” %} This release of Aleph introduced a couple of bugs that could make an Aleph instance unusable. Please skip this version in favour of newer Aleph versions. {% endhint %}

3.11.1

3.11.0

3.10.5

3.10.4

3.10.2

3.10.1

3.10.0

3.9.10

3.9.9

3.9.8

3.9.7

3.9.6

3.9.5

{% hint style=“warning” %} In this version, the OAuth configuration was changed in potentially breaking ways. Please read the instructions below for how to adapt your deployment. {% endhint %}

Aleph 3.9.5 uses OpenID Connect to largely automate the configuration of delegated login. Previous versions of Aleph configured an OAuth2 client explicitly, which also required coding custom handlers for each OAuth provider. The new system also addresses a number of potential security issues.

Unfortunately, the transition requires some incompatible changes:

Beyond these breaking changes, some other differences are notable:

Changes unrelated to OAuth:

3.9.4

3.9.3

3.9.1

3.9.0

3.8.9

{% hint style=“danger” %} Aleph 3.8.9 combines all database migrations before Aleph 3.2 into a single version. If you want to upgrade from an Aleph older than 3.2, we recommend you move via 3.8.0, upgrade to that version, before migrating across this version. {% endhint %}

3.8.6

3.8.5

3.8.3

3.8.1

3.8.0

3.7.2

3.7.0

3.6.4

3.6.3

3.5.0

3.4.9

3.4.0

3.0.0

The goal of aleph 3.0.0 is to harmonise the handling of data inside the index. Instead of having different formats and mappings for documents, entities, table rows and document pages, there is now just one type of index object: an entity.

This means that document-based data is now completely ‘translated’ to the followthemoney ontology used by aleph (meaning that in theory, each page of a document and each row of a table is now a node in the object graph of the aleph platform).

Upgrading

In order to accomplish this, a complete re-index is required in all cases. The recommended path of migrating from a 2.x.x installation is this set of commands in an aleph container shell (make shell):

Be advised that any data loaded via the entity mapping mechanism will need to be re-loaded after this. It is also worth noting that at OCCRP, we have now started generating mapped data via the followthemoney command-line tool, and are using alephclient to bulk-load the resulting stream of entities into the system. This has proven to be significantly quicker than the built-in mapping process.

Other changes