Released: 25 March, 2025
Feature Enhancements
New API for adding tags to Release Bundle v2 versions
You can now add a descriptive tag to a Release Bundle v2 version via REST API to help identify Release Bundle versions quickly. The tag will appear on the kanban board in the platform UI to enhance visibility and organization. For example, you can create tags such as
nightly-build,release-candidate,bugfix-2025-33124, and so on. For more information, see Assign Tag to Release Bundle v2 Version.New promotion icons on RLM Kanban board and timeline
New icons have been introduced to the Release Lifecycle Management kanban board and timeline. These icons indicate at a glance what type of Release Bundle promotion was performed (copy artifacts or move artifacts). Hovering over the icon provides a tooltip reminder. For more information, see Promote a Release Bundle (v2) to a Target Environment.
Organization Enforcement for OIDC GitHub Configuration
Artifactory now supports increased security for the OIDC GitHub integration by limiting authentication to a specified organization. You can avoid using this feature by selecting the Enable Permissive Configuration checkbox when configuring a new OIDC integration. For more information, see Configure an OIDC Integration.
SCIM Token Expiry Configuration
The JFrog Platform now supports the creation of SCIM tokens with configurable expiry times. To learn more, see Generate a Scoped Token for SCIM.
Additional Support for the PyPI JSON API
Artifactory now supports PyPI’s JSON API in virtual repositories.
Remote Repositories
Added Bearer Authentication support for remote repositories.
Resolved Issues
JIRA Issue | Component | Severity | Description |
|---|---|---|---|
Packages | Medium | Fixed an issue whereby triggering the Recalculation Index on an empty Conan local repository resulted in an error, increased the Conan metadata stuck tasks, and all packages that were uploaded after the reindexing were not indexed. | |
Packages | Medium | Fixed an issue whereby when retrieving the Packages.gz file from a virtual repository, sometimes old package information was retrieved, which lead to certain tools reporting old packages that no longer existed in the upstream. | |
Packages | Medium | Fixed an issue whereby when configuring a NuGet Remote Repository targeting community.chocolatey.org, no metadata was cached when executing the "choco outdated" command. | |
General | Medium | Fixed an issue whereby when a non-admin user using an include pattern would attempt to delete or overwrite a repository with an artifact in it that is already in the trash can, the action would fail. | |
RTDEV-51247 | Packages | High | Fixed an issue that prevented locally-generated properties of various package types from being replicated. |
RTDEV-54260 | Packages | Medium | Fixed an issue whereby non-admin users were unable to create a Debian snapshot for a virtual repository. |
RTDEV-54091 | Packages | Medium | Fixed an issue whereby a user who does not have delete permissions would receive a 200 successful status code when calling the Promote Docker Image API with a copy:false parameter, even though certain artifacts were not removed from the source repository. Now, when this happens, the API returns a 206 status code, indicating partial success because the promotion was executed successfully but insufficient permissions prevented the deletion of certain artifacts from the origin repository. |
JA-16503 | General | Medium | Fixed an issue whereby when the Authentication provider name contained a space character it did not render the configuration page. |
JA-16359 | General | Medium | Fixed an issue whereby group information for a selected user was not displayed. |
JA-16274 | Platform Management | Medium | Fixed an issue where project access tokens were not getting revoked when the user who created them was removed. |
JA-16151 | Projects | Medium | Fixed an issue whereby project scope access tokens were visible from the Project Admins profile. |
JA-16046 | Platform Management | Medium | Fixed an issue whereby federated reference token authentication was not working correctly in Event APIs. |
JA-15292 | User Interface | Medium | Fixed an issue whereby there was no syntax validation for the OIDC provider URL. |
JA-13245 | User Interface | Medium | Fixed an issue whereby a Crowd user would get an internal server error when trying to unlock a user profile with a dummy or incorrect password. |