Skip to content

Releases: alephdata/aleph

4.1.7

27 Oct 15:44
4.1.7
7ebc131

Choose a tag to compare

What's Changed

Full Changelog: 4.1.6...4.1.7

4.1.6

07 Aug 13:59
4.1.6
4f00df6

Choose a tag to compare

This release fixes some issues related to Aleph's maintenance mode.

What's Changed

  • Bugfix: maintenance mode permission checks for collection and export creation by @stchris in #4279
  • Bugfix: prevent constant refetching of profile information in maintenance mode by @stchris in #4280

Full Changelog: 4.1.5...4.1.6

4.1.5

14 Jul 09:03
4.1.5
eeb30ad

Choose a tag to compare

What's Changed

Full Changelog: 4.1.4...4.1.5

4.1.4

01 Jul 07:30
4.1.4
4058694

Choose a tag to compare

What's Changed

Full Changelog: 4.1.3...4.1.4

4.1.3

12 Jun 17:35
82f5bba

Choose a tag to compare

This Aleph release updates the default version of ingest-file in the Docker Compose configuration and Helm chart to ingest-file 4.1.2.

Important

Prior versions of ingest-file contain a security vulnerability due to insecure handling of 7zip archives. We recommend that you update Aleph instances you operate to use the latest patched release of ingest-file.

Please refer to the release notes of ingest-file 4.1.2 for details.

Full Changelog: 4.1.2...4.1.3

4.1.1

22 Apr 12:21
4.1.1
0d8d7d6

Choose a tag to compare

What's Changed

Full Changelog: 4.1.0...4.1.1

4.1.0

04 Apr 14:21
4.1.0
d7812f6

Choose a tag to compare

Upgrade instructions

Important

If you use the Aleph API, make sure to carefully review the following upgrade instructions.

Aleph 4.1 introduces changes to API keys:

  • Users can now regenerate their API key from the user settings page.
  • New API keys now expire automatically after 90 days. In order to continue accessing the Aleph API, users need to regenerate their API key before it expires. Users will receive email notifications 7 days before their API key expires, as well as on the day it expires.
  • Users can only see their API key directly after it has been generated, but not again after that.
  • New users won’t have an API key by default anymore, they need to actively generate an API key.

After upgrading to Aleph 4.1, to continue using existing API keys, you need to run the following command in an Aleph container:

aleph hash-plaintext-api-keys

Existing API keys won’t expire automatically, but you can optionally set them to expire after 90 days by running the following command in an Aleph container:

aleph reset-api-key-expiration

What's Changed

Full Changelog: 4.0.2...4.1.0

4.0.2

23 Nov 13:17
4.0.2
6610201

Choose a tag to compare

We're announcing the release of Aleph 4.0.2 (and ingest-file 4.0.2) and highly recommend users of the 4.x branches to update to this release.

What's changed

  • Update to servicelayer 1.23.2 which fixes a significant performance regression noticeable especially when there are > 10000 tasks per dataset being processed

Full Changelog: 4.0.1...4.0.2

4.0.1

07 Nov 10:23
4.0.1
e790959

Choose a tag to compare

We're announcing the release of Aleph 4.0.1 (and ingest-file 4.0.1) and highly recommend users of the 4.x branches to update to this release.

What's changed

Bugfix

  • Update to using servicelayer 1.23.1 which fixes an issue with improper clean-up when a task exhausts it's maximum number of retries

Full Changelog: 4.0.0...4.0.1

4.0.0

15 Oct 10:24
4.0.0
d452633

Choose a tag to compare

Hello Aleph community! We’re excited to announce Aleph 4.0.0, a release focused on powerful new features, performance improvements, and expanded options for investigation sharing and user metrics. In addition, this release includes a few other small enhancements, bug fixes and dependency upgrades.

🚀 Bigger Changes 🚀

  • RabbitMQ based task queueing backend
    • Configurable AlephWorker Stages
    • Priority Buckets for Processing
    • System Status Page Enhancements
  • Updated Prometheus Metrics
  • Documentation Restructure and Enhancements
  • Improved Error Handling in Elasticsearch Upgrades

As always, we’d love to hear your feedback to keep improving. Feel free to reach out and share your thoughts!


What's Changed

Features

RabbitMQ

4.0.0 introduces a change to the way background tasks are scheduled. Previously Aleph used a Redis-based task queue, which was well designed but showed its limitations with large payloads and a risk of data loss. RabbitMQ queues are persisted to disk, but the flexibility in the way messages are queued, routed and fetched allows for certain optimizations which Aleph benefits from because of the widely varying degree of task loads.

Migration notes from Redis to RabbitMQ

Due to the significant changes in terms of task status persistence, switching between Aleph versions with RabbitMQ and Redis-based task queues requires some manual steps in order to ensure data consistency.

Perform the following steps every time you are either upgrading to a version with the RabbitMQ task queue or rolling back to the Redis-based task queue:

  1. Let all pending jobs run to completion (check the status page).
  2. Put Aleph into maintenance mode.
  3. Stop all workers (worker, ingest-file processes).
  4. (optional) Save the current state of redis in case you want to roll back using the BGSAVE command.
  5. Clear Redis (by issuing FLUSHDB from redis-cli from the redis container). If you get the error message "Unknown command FLUSHDB" then this command is disabled and you can resort to this shell invocation: echo 'KEYS *' | redis-cli | grep -v '^aleph:' | sed 's/^/DEL /' | redis-cli.
  6. (optional, if previous versions had conflicting RabbitMQ queue settings) Delete existing queues using rabbitmqctl delete queue {ingest,pruneentity,updateentity,exportxref,analyze,flushmapping,reingest,exportsearch,index,xref,reindex,loadmapping}. NOTE: queues are named after the stages found in ALEPH_WORKER_STAGES.
  7. Perform the upgrade or rollback to the desired version of Aleph.
  8. Ensure that all expected processes have started correctly.

Related changes:

Prometheus metrics

We have extended the Prometheus metrics exposed by Aleph to provide more information about active users and the data in your Aleph instance. For example, you can now query for the number of active users within the past 30 days or the number of investigations related to a particular language. For details about the available metrics please refer to the metrics reference in the technical documentation.

Sharing investigations

Due to the sensitive nature of dataset access we have made some changes to the way datasets are shared, no longer allowing email addresses to autocomplete. This means one needs to know the exact email address of another user if they want to share an investigation.

  • Feature: Allow sharing of investigations by @tillprochaska in #3865
  • Remove sharing options from create investigation screen by @stchris in #3862
  • Multiple small UX enhancements related to investigation sharing/user suggestion component by @tillprochaska in #3868

Other new features

Bug fixes and other changes

Documentation updates

Dependency updates

Full Changelog: 3.17.0...4.0.0