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
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
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.
Learn more about authenticating to Container registry with GitHub Actions
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.
Learn more about configuring visibility for container images
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.
