Feature

Artifact Registry is available in the europe-north2 region (Stockholm). For more information, see Global locations.

Issue

Artifact Registry might give a 400 error on pushes or pulls for Workforce Identity Federation users. This issue is caused by Workforce Identity Federation attribute mappings in the Artifact Registry URL causing problems on the backend.

To mitigate this issue, you can push or pull from Artifact Registry without attribute mappings, or reduce the length of your attribute mappings.

Feature

Organization policy constraints for Artifact Registry is available in General Availability.

For more information, see Use custom organization policies.

Feature

Artifact Registry support for OCI specifications v1.1 is generally available in Docker format repositories.

You can upload containerized metadata about another container image to Artifact Registry as an attachment. To learn more, see Manage container metadata.

Change

Updates to the Artifact Registry API are as follows:

• Add or update file annotations with UpdateFile().
• Add or update package version annotations with UpdateVersion().
• Filter by annotation or name with ListFiles(), ListPackages(), and ListVersions().
• Filter by name with ListTags(), ListRepositories() and ListDockerImages().
• Order by name, createTime, or updateTime for ListFiles(), ListVersions(), ListRepositories(), and ListPackages().

Change

The following Artifact Registry Cloud Audit Log method names have changed:

• Docker-EmptyTarBlob is renamed Docker-ServeBlob
• Docker-GetEmptyTags is renamed Docker-GetTags
• Docker-HeadEmptyTarBlob is renamed Docker-HeadBlob
• Kfp-UploadPackage-Redirect is renamed Kfp-UploadPackage
• Apt-ViewRemoteIndexFile is renamed to indicate the type of file requested:
  • Apt-ViewIndexFile: when a repository metadata file is requested
  • Apt-Contents: when the Contents index file for a specific repository component and architecture type is requested
  • Apt-ViewArchIndexFile: when the Packages index file for a specific repository component and architecture type is requested
• Apt-ViewRemotePackageFile is renamed Apt-ViewPackageFile
• Yum-ViewUpstreamFile is renamed to indicate the type of file requested:
  • Yum-ViewIndexKey: when the public key for signing Yum packages is requested
  • Yum-ViewIndexFile: when one of a repository's index files is requested
  • Yum-ViewPackageFile: when a Yum package file is requested

For more information on Artifact Registry logs, see Audit Logging.