packages

Subscribe to all “packages” posts via RSS or follow GitHub Changelog on Twitter to stay updated on everything we ship.

~ cd github-changelog
~/github-changelog|main git log main
showing all changes successfully

GitHub Packages Container registry, ghcr.io, is now generally available! Container registry provides the best developer experience for publishing, managing, and consuming containers on GitHub. For more information, check out the Container registry general availability blog post.

Learn more about GitHub Container registry

For questions, visit the GitHub Packages community

To see what's next for Packages, visit our public roadmap

See more

On June 5th, 2021 the GitHub Container Registry, ghcr.io, will be put into maintenance mode. The maintenance window will occur from 16:00 – 17:30 UTC. During this short time pushes to the service will be blocked, however pulls or downloads will remain available. For more detailed status information during maintenance, please refer to https://githubstatus.com

Learn more about GitHub Container Registry

For questions, visit the GitHub Packages community

To see what's next for Packages, visit our public roadmap

See more

You can now use GITHUB_TOKEN to authenticate with the Packages Container registry in your Actions workflows. Say goodbye to all those PATs (delete them from your profile too!), and say hello to using the GITHUB_TOKEN in your workflows to read, create, update, and delete containers.

      - name: Login to Packages Container registry
        uses: docker/login-action@v1 
        with:
          registry: ${{ env.REGISTRY }}
          username: ${{ github.actor }}
-          password: ${{ secrets.PAT }}
+          password: ${{ secrets.GITHUB_TOKEN }}

Write and read access of Actions to containers can be managed in the container settings.

manage actions access animation

Learn more about authenticating to Container registry with GitHub Actions

For questions, visit the GitHub Packages community

To see what's next for Packages, visit our public roadmap

See more

The GitHub Packages Container registry can now create and use containers set with Internal visibility. Internal visibility allows all members of an organization and all organizations within an enterprise read access to the container to more easily share data with your teammates.

This feature is generally available today on GitHub Enterprise Cloud. Navigate to your organization's Packages settings and click the option for Internal visibility to enable.

image

Learn more about configuring visibility for container images

For questions, visit the GitHub Packages community

To see what's next for Packages, visit our public roadmap

See more

The Packages npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.

Learn more about the Packages npm registry

For questions, visit the GitHub Packages community

To see what's next for Packages, visit our public roadmap

Note: This post originally inaccurately referred to time as not being returned in the “official npm specification”. While an “official npm specification” does not exist, time is referred to in the registry package-metadata documentation and used for some commands.

See more

You can now delete and restore any package type within GitHub Packages, even publicly visible packages. Any package or package version of yours can now be deleted through the github.com website or REST APIs. The ability to delete any package will help you manage the packages you want to keep in your account. Any package deleted within the last 30 days can also be restored to undo a delete and bring the package back to its original state.

Learn more about deleting and restoring packages and Packages REST APIs

For questions, visit the GitHub Packages community

To see what's next for Packages, visit our public roadmap

See more

As more and more versions of containers are published it can become harder to find the tagged images in between a long list of untagged images which create a lot of noise. Now when you visit the version list page of a container, like the super-linter versions, you'll see options for listing tagged, untagged, and all images. We default to showing only the tagged images on the version list page to keep the list limited to the most important images.

This filtering is only available for GitHub Packages containers (beta).

See more

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.

See more