Artifactory 7.96.3 Cloud

JFrog Release Information

Content Type
Release Notes
ft:sourceType
Paligo

Released: 30 September, 2024

Breaking Change when Using Get User Details API for Details of Non-Logged-In Users

When retrieving user details for non-logged-in users via the Rest API, a random date in the distant past was returned, now a null value will be returned. Previously, if a user never logged, in the response to the Get User Details API, the value of last_logged_in was 1970-01-01T00:00:00.000Z. Now, if a user never logged in, the value of last_logged_in will be null.

Feature Enhancements

  • Improved Cargo Status Code Responses

    Cargo status code responses are now aligned with the cargo registry according to the Cargo specification.

  • The Hugging Face readme.md file is now accessible

    The Hugging Face readme.md file can now be viewed with an MD viewer for Hugging Face packages.

  • Significant Improvements in Deploying Artifacts from Archives

    The Deploy Artifacts from Archive REST API now supports deploying artifacts in parallel threads as well as sequentially, significantly reducing the time it takes to deploy. For more information, see Deploy Artifacts from Archive.Deploy Artifacts from Archive

  • Adding pagination to Release Bundle v2 Version Details REST API

    The REST API for getting Release Bundle v2 version details now includes the ability to paginate the results using the offset and limit query parameters. In addition, the response now includes the total_artifacts_count.Get Release Bundle v2 Version Details

  • Improved Failure Retry Mechanism when working with Google Cloud Storage

    The google-storage-v2 provider now supports an improved retry mechanism when Google Cloud Storage returns 50x errors. Two new parameters have been added to the provider (maxRetries and retryIntervalMillis) to allow configuring this. For more information, click here.Google Storage Binary Provider Native Client Template

Resolved Issues

JIRA Issue

Component

Severity

Description

RTFE-1908

User Interface

Medium

Fixed an issue whereby users could not access the Artifactory->Artifacts tab when upgrading to a new Artifactory version.

RTFE-1790

Packages

Medium

Fixed an issue whereby the command to install a Go package on the Package Version Details was incorrect.

RTFACT-30720

Packages

Medium

Fixed an issue whereby a Go remote repository was not able to proxy Go providers with package versions similar to v2.0.0-beta.1.

RTFACT-30701

Packages

Low

Fixed an issue whereby the Artifactory webhook did not trigger an event for list.manifest.json after pushing a multi-arch Docker image.

RTFACT-30677

Platform Management

Medium

Fixed an issue whereby the Access REST API returned a "403 Forbidden" error when attempting to delete an AWS IAM Role.

RTDEV-47642

Repositories

Medium

Fixed an issue where when using Terraform with remote Terraform repositories and anonymous access enabled, permissions did not behave as expected. This may impact users ability to access these repositories.

RTDEV-47455

General

Medium

Fixed an issue whereby certain RPM Packages were not listed in a remote repository when pointing to the Rockylinux registry.

RTDEV-46817

General

Medium

Fixed an issue whereby when a storage quota notification could not be sent to a project admin because there was no email address for the project admin, the notification was also not sent to other project members who did have email addresses.

RTDEV-46671

Storage

High

Fixed an issue related to S3 Cold Storage whereby Artifactory failed to move packages to the Glacier Tier.

RTDEV-46343

Packages

Medium

Fixed an issue whereby Artifactory's "reject invalid jars" feature was incorrectly rejecting archives with a payload before the zip structure.

JA-14387

General

Medium

Fixed an issue whereby when creating a new OIDC integration with a name that is a prefix of an existing integration, all the mappings from the existing integration were automatically copied over to the new integration.

JA-14163

Platform Management

Medium

Fixed an issue whereby when retrieving user details for non-logged-in users via the Rest API, a random date was returned for the time of the last login. Now null is returned for a non-logged-in user.