aleph 4.1.0 released

aleph 4.1.0 released

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: Comparing 4.0.2...4.1.0 · alephdata/aleph · GitHub