0.2.6
Important Notes:
- The new environment variable
PERSONAL_ACCESS_TOKEN_JWT_SECRET
has been added.
Make sure to configure it in your Helm or Docker Compose setup under the server environment variables.- The
HASH_NONCE
environment variable is no longer required. You can safely remove it from your configuration. However, keeping it will not break anything, so updating it is recommended but not mandatory.
Features
- Personal Access Tokens: RepoFlow now supports Personal Access Tokens, which provide a secure and flexible alternative to passwords for authentication. These tokens can be created in the new Account Settings under Access Tokens. They can be used in place of passwords for Basic Authentication (where the username becomes irrelevant) or as a Bearer token for API requests and package downloads, offering versatility similar to Basic Auth.
- New Documentation: Added two new pages for Helm, focused on production use. These pages explain how to configure your own Object Storage and PostgreSQL instance.
- Added support for labels in Docker images. RepoFlow now extracts and displays certain labels on the package page, such as:
org.opencontainers.image.description
,org.opencontainers.image.licenses
,org.opencontainers.image.source
Bug Fixes
- The
S3_END_POINT
variable in the Helm chart had a bug that prevented it from being overridden throughvalues.yaml
, which has now been resolved.