Skip to main content

0.9.0 (Pre Release)

Upgrading from an earlier version?​

If you are upgrading an existing deployment, review the upgrade notes first.

Features (6)​

  1. Audit Logs
    Added a new audit log table to make system-wide action monitoring easier.

  2. Migration Center
    Added support for running repository migrations directly in RepoFlow without the CLI, with a guided UI, better migration visibility, and broader source support including Artifactory, Nexus 2, Nexus 3, and Verdaccio.

  3. Download Rules
    Added custom download rules that can block or hide package downloads based on repository, package, version, metadata, age, scan status, and vulnerability conditions, helping teams reduce supply chain risk.

  4. Remote Cache Package Browsing
    Remote repositories now expose cached packages in the UI, including package metadata, similar to local repositories.

  5. Repository File Browser
    Improved file browsing for both local and remote repositories, making it easier to inspect stored files and cached upstream contents.

  6. Remote Package Scanning
    Remote cached packages can now be scanned for vulnerabilities.

Improvements (9)​

  1. Workspace Limit Visibility
    Workspace settings now highlight usage in an alert color when current usage exceeds a configured limit.

  2. User Delete Confirmation
    Deleting a user from the System Settings Users tab now shows a confirmation popup, matching the existing workspace delete flow.

  3. Faster Docker Remote Pulls
    Docker remote repositories now make authenticated pulls feel smoother by avoiding unnecessary repeated authentication round-trips during the same pull, which can improve pull performance for remotes such as Docker Hub.

  4. Clearer Docker Remote Rate Limit Errors
    Docker remote pulls now return clearer Docker-compatible errors when an upstream registry rate limit is reached, helping users distinguish remote rate limiting from missing images or cache files.

  5. Clickable Authentication Labels
    The SSO and LDAP setup checkboxes in System Settings can now be toggled by clicking their label text.

  6. Improved Responsive Layouts
    Updated page layouts to make better use of available screen space across more viewport sizes.

  7. Faster API Requests
    Added short-lived API response caching to improve server performance while keeping permission changes responsive. By default, permission-related changes may take up to 1 second to take effect, and the cache duration can be configured with a server environment variable.

  8. More Efficient Database Structure
    Improved the internal database structure to reduce storage usage and make repository file records more efficient.

  9. AWS S3 Credential Options
    AWS S3 storage can now use the AWS SDK default credential chain when S3_ACCESS_KEY and S3_SECRET_KEY are omitted, enabling setups such as EC2 instance profiles, ECS task roles, and EKS web identity/IRSA. Temporary AWS credentials are also supported via the new S3_SESSION_TOKEN environment variable.

Bug Fixes (3)​

  1. NuGet Package Filename Handling
    Fixed Nexus 3 NuGet migrations so package filenames are derived correctly from package metadata instead of repository asset paths.

  2. Password Manager Interference
    Reduced browser password-manager prompts in the migration source step and prevented stuck password UI when moving between steps.

  3. Docker Repository File Names
    Fixed a typo where some Docker repository manifest files were stored and shown as menifest instead of manifest.

Upgrade notes​

RepoFlow 0.9.0 is an early beta pre-release. Please do not upgrade production environments to this version. Use it only in a new testing environment, or wait for the full stable release before upgrading production deployments.

Before upgrading, we recommend taking a fresh backup of both your database and S3-compatible storage. This is always a good practice for self-hosted upgrades, and it is especially useful for this release because the upgrade includes database changes that touch repository file records.

If you run RepoFlow with multiple server pods, temporarily scale the server down to one pod for the upgrade so only one instance applies the startup migrations. After the upgraded server starts successfully, you can scale back to your usual high-availability setup.

For installations with very large numbers of stored files, for example millions of file records, the first server startup after the upgrade may take a few extra minutes while the database migrations complete.

Important: The legacy RepoFlow API is no longer supported. Starting with this version, only API v1 is supported. All package management APIs remain unchanged. Commands such as docker push, npm publish, nuget push, mvn deploy, and similar package publishing workflows continue to work exactly as before.

However, if you previously used the RepoFlow API directly for actions such as uploading packages, managing repositories, or other administrative operations, those requests must now use API v1.

API v1 is very similar to the previous API, and in most cases updating the endpoint URL will be sufficient. At the same time, the API structure has been improved to provide a better developer experience, including clearer organization, more detailed error responses, and improved documentation.

If you have any questions or need help migrating to API v1, feel free to contact us.