Released: 13 October, 2024
New Features
Cleanup Policies
JFrog Cleanup Policies enable Platform and Project Administrators to define and customize policies based on specific criteria for removing unused binaries from across their JFrog platform. This provides control over storage utilization and ensures optimal system performance. By setting specific criteria and rules, administrators can customize a repeatable cleanup process that aligns with their organization's requirements. For more information, click here.
Support for Multi-Architecture Tag Deletion
Artifactory now supports deleting multi-architecture Docker and OCI image tags with one action. For more information, see Delete Multi-Architecture Docker Tags.
Feature Enhancements
Cannot modify or delete files that belong to a promoted Release Bundle v2
To protect the immutability of Release Bundles v2, users are now blocked from modifying or deleting a file that belongs to a promoted Release Bundle. Users must first delete the promotion or delete the Release Bundle version altogether before the files can be modified or deleted.
Release Bundles v2 protected from expired GPG keys
When a user attempts to create, promote, or distribute a Release Bundle v2 version, the action is now blocked if the GPG key has expired.
Cargo index/config.json API Aligned with the Cargo Specs
The Cargo index/config.json API has been aligned to the Cargo specs so that it now returns a response even if a user has no permissions on a repository and invokes an auth-challenge.
New worker services
New dedicated workers now support the BeforePropertyDelete and BeforeDelete events.
Support for OIDC Forward Proxy Configuration
The JFrog Platform OIDC integration now supports the configuration of a forward proxy. For more information, see Manage Proxy Servers.
Resolved Issues
JIRA Issue | Component | Severity | Description |
|---|---|---|---|
RTFE-1940 | Repositories | Medium | Fixed an issue whereby the Set Me Up page showed the wrong URL for Docker repositories with a sub-domain method configured in SaaS. |
RTFE-1918 | User Interface | Medium | Fixed an issue whereby the Set Me Up page would get stuck when clicking on “Generate Token & Create Instructions”. |
General | Medium | Fixed an issue whereby, items were not displayed in a native browser in virtual repositories but were displayed in a native browser in local repositories. | |
Packages | Medium | Fixed an issue whereby a Yum virtual repository was unable to merge data from its repositories when one of the repositories specified the location of index files in repomd.xml using end tags instead of self-closing tags. | |
RTDEV-48547 | Federated Repositories | Medium | Fixed an issue where the pairing token was using base URL for federated repo binding end point instead of federated base URL. |
RTDEV-48273 | Packages | Medium | Fixed an issue whereby default features in Cargo.toml were overwritten as true when the JSON file was deleted from the .cargo folder in the repository. |
RTDEV-48199 | General | Medium | Fixed an issue whereby requests reaching Artifactory that contained no headers or null values returned a 500 error and “java.lang.NullPointerException” appeared in Tomcat logs. |
RTDEV-47968 | General | High | Fixed an issue whereby after upgrading to 7.90.9, users could not retrieve the latest artifact and would receive a '404 file not found' error. |
RTDEV-47967 | Packages | Medium | Fixed an issue whereby installation of Huggingface modules was not working when using smart repository configuration. |
RTDEV-47671 | Builds | Low | Fixed an issue whereby build promotion failed when the same artifact was used in the build more than once. |
RTDEV-47286 | Packages | Medium | Fixed an internal logging issue with PyPI metadata uploads. |
RTDEV-47144 | Packages | Low | Fixed an issue whereby when attempting to download an artifact from a VCS remote repository in Artifactory with an exclude/include pattern set, the download request failed with a 404 Not Found error but the error message did not state that the artifact was not downloaded due to the exclude/include pattern. |
RTDEV-48582 | Repositories | Critical | When deploying a new chart to helm local repositories, the index.yaml did not update (re-index is not occur). This may happen if the lock time reached the time limit configured in the following system property ha.shift.events.lock.lease.period.minutes (default value is 30 minutes). |
JA-14274 | Authentication Providers | High | Fixed an issue whereby, when mTLS is enabled in Artifactory and the Router port (8082) is accessed, the mTLS user is not created in the Artifactory users list. However, the user is created when accessing the Artifactory port (8081). |
JA-14175 | Authentication Providers | Medium | Fixed an issue whereby the Crowd login failed when the Crowd server was unavailable during Artifactory restart. It may take a few minutes for the Crowd login to become available once the Crowd server restarts. |
INST-8061 | Installation | Medium | Fixed an issue whereby the artifactory-ha chart had hard-corded values of --max-time 1 for livenessProbe and startupProbe. |
EVT-1211 | Builds | Medium | Fixed an issue whereby selecting the Any Build checkbox in the UI caused the complete list of builds to be injected instead of simply setting the anyBuild parameter to true. |