From hosting private packages in a private repository to tightening your security profile with GITHUB_TOKEN, here are five simple ways you can streamline your workflow with GitHub Packages.
Throughout the beta, we added features to improve the experience of using the Container registry. Today, we’re excited to announce that the Container registry is generally available as part of GitHub Packages!
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…
We're renaming GitHub Package Registry (GPR) to GitHub Packages. This change is reflected on [GitHub.com](https://www.github.com), in the APIs and webhooks
We’ve introduced the ability to proxy packages from the npm registry through GitHub Package Registry for easier configuration and consolidation. Read more about the change and opt in to try it out.
You can now use a `GITHUB_TOKEN` when publishing or installing a npm or Apache Maven package to GitHub Package Registry from a GitHub Action. You can also publish or install packages…
Today we’re excited to announce that we’ll be adding support for Swift packages to GitHub Package Registry. Swift packages make it easy to share your libraries and source code across your projects and with the Swift community.