Released July 28, 2024
New Features
Distribution Service Monitoring
Administrators can now monitor the status of all active and previous distribution operations, including the size and duration of the operation. This capability lets you see, for example, which distributions are currently in progress, which are pending an Xray scan, and which have been completed. For more information, see Monitor the Distribution Service.
Feature Enhancements
Default path mapping from the last promotion
An enhancement has been implemented to the default path mapping method when distributing and exporting Release Bundles v2. When this feature is enabled, the default destination repositories from the last successful promotion, if one exists, will be displayed in the UI. You can change this mapping if desired. If no such promotion has been performed, the path mapping fields in the UI are left blank, and the default destination repositories will match those at the source, as before.
You can modify or remove this suggested default before executing the distribution or export operation. For more information, see Distribute a Release Bundle (v2) using the Platform UI.
A new configuration parameter,
default-path-mapping-by-last-promotion
(default=false) has been introduced to support this feature. Additionally, this parameter can be included as a request parameter in the Distribute Release Bundle Version v2 API to enable the feature for specific requests, facilitating a gradual rollout of this feature. For more information, see Distribution Application Config YAML File.Note
If the request parameter is configured in the API, this setting overrides the configuration parameter in the YAML file.
Distribute Release Bundle v2 Version UI enhancements
The Distribute Release Bundle v2 dialog box features the following enhancements:
A new checkmark icon next to the distribution target indicates that the selected Release Bundle version has already been distributed to that target. It is still possible to distribute the same version again to that target.
A change to the buttons in the dialog box now requires you to review the path mappings before executing the distribution action.
New metrics for tracking distribution failures
New metrics that keep a running count of distribution failures due to user-related and application-related errors have been added. These metrics make it possible to track what types of issues are preventing the successful completion of distribution operations. For more information, see Distribution Open Metrics Support.
Sanitizing Markdown release notes
When adding release notes in Markdown to a Release Bundle v1, users are restricted from inserting HTML tags to prevent security risks. This behavior is controlled by a new configuration property (
enable-sanitize-release-notes
), which is set totrue
by default.Support for PostgreSQL v16
JFrog Distribution has been certified for use with PostgreSQL v16.
Bug Fixes
Jira Ticket | Severity | Description |
---|---|---|
JR-9102 | Medium | Fixed an issue whereby the response from Artifactory to an AQL query fetching artifacts sometimes included properties with null values, which led to errors. |
Resolved Vulnerabilities
This release contains resolved CVEs (security vulnerability issues). For more information:
Resolved CVEs that impact JFrog Distribution
Resolved CVEs that do not impact JFrog Distribution