Released: 29 August, 2025
Feature Enhancements
Support for webhooks for project-related builds
Artifactory now supports the creation of webhooks for builds associated with specific projects. This enables you to receive notifications whenever a build in a particular project is uploaded, promoted, or deleted. To create a build webhook for a specific project, you must be working within the scope of the project (as opposed to All Projects).
For specific guidelines about creating a build webhook for a specific project, see Domain: Build.
Change in API response for Release Bundle v2 tags
To correct inconsistent behavior, the following API endpoints have changed the response for Release Bundle v2 tags from
bundle_tagandrelease_bundle_tagto a standard response oftag:Evidence propagation to Federation members
This release enhances the Evidence service to enable evidence propagation to all Federation members, regardless of whether they contain the relevant public key for verification. Evidence verification, however, is performed only on those members that have the public key. For more information, see Verify Evidence.
RPM Package Settings
Added support for Administrators to enable/disable RPM package settings for the following:
Recommends Tags
SHA256
For enabling/disabling these settings, see Enable/Disable RPM Package Settings.
Curation Support for NuGet Virtual Repositories
Extended JFrog Curation capabilities to support NuGet virtual repositories, providing a powerful, centralized way to secure your NuGet package consumption.
UI Support for Debian Source Package Search
Added support for Debian Source package search.
Improvement in VCS Remote Repositories
The GitHub Server option for Git providers was added for VCS remote repositories. For more information, see Additional Settings for VCS Remote Repositories.
Improvement to the Vendor Folder for the Private Go Registry and the Go Proxy
Checksums in the private Go registry and the Go proxy are now aligned for the Go version 1.24 vendor folder.
Updated Artifactory Worker Events
Updated the following Worker Events:
After Copy: The following fields are removed from the Sample Payload:
contentLength,trustServerChecksums,servletContextUrl,skipJarIndexinganddisableRedirect.After Delete: The following field is removed from the Sample Payload:
headersAfter Property Create: The following fields are removed from the Sample Payload:
contentLength,trustServerChecksums,servletContextUrl,skipJarIndexing,disableRedirectandheaders.After Move: The following fields are removed from the Sample Payload:
contentLength,trustServerChecksums,servletContextUrl,skipJarIndexinganddisableRedirect.Before Move: The following fields are removed from the Sample Payload:
contentLength,trustServerChecksums,servletContextUrl,skipJarIndexinganddisableRedirect.
Resolved Issues
JIRA Issue | Component | Severity | Description |
|---|---|---|---|
RTFE-3636 | Packages | Medium | Fixed an issue whereby the Set Me Up repositories list was not showing an empty virtual Maven repository. |
RTFE-3634 | Federated Repositories | Low | Fixed an issue whereby when converting a local repository to a federated repository, a warning message appeared that “This operation cannot be undone” even though the federated repository can be reverted back to a local repository. |
RTFE-3603 | Projects | Medium | Fixed an issue whereby the "Read Only" check box was not saved when sharing a repository with a project. |
RTFE-3546 | User Interface | High | Fixed an issue whereby the warning “<previous artifact from previous project> could not be found“ was incorrectly appearing in the UI when switching projects. |
General | Medium | Fixed an issue whereby when Artifactory attempted to authenticate a remote Sonatype Nexus repository using Basic Authentication, the request failed with a 401 Unauthorized error if the username contained non-ASCII characters. | |
RTDEV-61511 | Release Lifecycle Management | Medium | Fixed an issue whereby promotion to a specific repository would fail due to a race condition caused by the creation of an unrelated repository in the same environment. |
RTDEV-61351 | Release Lifecycle Management | Medium | Fixed an issue whereby creating a Release Bundle containing two builds with different tags but identical content resulted in the inclusion of just one build. |
RTDEV-61209 | Release Lifecycle Management | High | Fixed an issue whereby the Get Release Bundle v2 Versions in a Specific Environment API would return data that did not reflect the version's current environment. |
RTDEV-61179 | General | Medium | Fixed an issue whereby Support Bundle status in the UI was reported as FAILURE despite successful Support Bundle generation. |
RTDEV-59071 | Packages | Medium | Fixed an issue where an external user could obtain an API key instead of an Identity Token in the Maven Set Me Up tool. |
RTDEV-58946 | Release Lifecycle Management | Medium | Fixed an issue where creating a Release Bundle would incorrectly discard duplicate artifacts from different modules. If a build contained the same artifact in multiple paths, only one copy was kept. The process now correctly includes all instances of the artifact, preserving each one in the final Release Bundle. |
JFUI-18900 | General | Medium | Fixed an issue whereby a custom message enabled in the UI would cause the "The Federated repository settings are not synchronized between these repositories" notification to negatively impact the user experience by expanding and blocking other elements. |
JA-18037 | User Management | High | Fixed an issue whereby clicking Unlock on the Edit Profile page was throwing a 403 Forbidden error. |