Artifactory 7.131.0 SaaS

JFrog Release Information

Content Type
Release Notes

Released: 30 December, 2025

Feature Enhancements

  • Release Bundle v2 creation dry run

    You can now use the Create Release Bundle v2 REST API to perform a dry run, which simulates the creation of the Release Bundle and performs all the necessary validations, but without persistence. For more information, see Perform a Release Bundle v2 Creation Dry Run.Create Release Bundle v2 VersionPerform a Release Bundle v2 Creation Dry Run

  • Curation Support Added for PHP Composer Remote Repositories

    Artifactory now ensures security compliance for Composer repositories protected by JFrog Curation. If a package is blocked by security policy, Artifactory automatically prevents the Composer client from falling back to external source URLs to download.

    This feature requires Xray version 3.137.0 or above.

  • Logging of Administration Configuration Changes

    The JFrog Platform now supports logging of any changes made to the access configuration, such as enabling anonymous access, in the Access audit trail log.Audit Trail Log

Resolved Issues

RTDEV-69828

Release Lifecycle Management

Low

Fixed an issue that prevented users from using multiple filters to exclude specific packages when patching a Release Bundle.

RTDEV-69500

Repositories

Medium

Fixed an issue whereby attempting to delete a non-existing artifact resulted in status code 204 (No Content) rather than 404 (Not Found).

RTDEV-68382

Packages

Medium

Fixed an issue in which Docker range uploads returned an incorrect range start offset.

RTDEV-67140

Builds

Medium

Fixed an issue that prevented Project Administrators from defining webhooks for build events within their assigned project.

RTDEV-66745

Packages

Medium

Fixed an issue whereby Helm layout enforcement was not working on federated Helm repositories.

RTDEV-65894

Packages

Medium

Fixed an issue in which a user could retrieve certain metadata files from a Debian virtual repository using the anonymous user, even though the user lacked proper permissions.

JIRA Issue

Component

Severity

Description