You can now more easily opt-in to the public beta of GitHub Packages' improved containers experience. New users and organizations can opt-in to the beta for their organization using either organization settings, or for their user account using user feature preview.
Current organizations and users of the Packages containers beta will be automatically opted-in for continued access to service.
See Enabling improved container support for more information.
If your organization uses IP allow lists to restrict access, GitHub Packages now respects those settings.
We've refreshed the landing page for containers in GitHub Container Registry. You can now see an organized snapshot of the description, versions, tags, and downloads.
You can also connect your containers to a repository via an OCI label or through the UI. The landing page will show relevant links and content from the linked repository.
In addition to deleting private packages through the GraphQL API, you can now delete private packages when navigating to your repository’s packages on github.com. See our guide in GitHub Help for more.
We’re renaming GitHub Package Registry (GPR) to GitHub Packages. This change is reflected on GitHub.com, in the APIs and webhooks:
– There is a new PackageEvent in the Events API which replaces the existing event RegistryPackageEvent.
– There is a new package webhook which replaces the existing registry_package webhook.
– The GraphQL API schema is also changing to reflect the new name.
Starting today, GitHub Packages (formerly GitHub Package Registry) is generally available. The use of GitHub Packages is free for all public repositories, and every plan gets included storage and data transfer for private repositories.
