Media releases are provided as is by companies and have not been edited or checked for accuracy. Any queries should be directed to the company itself.
  • 15 May 2019 13:07

Introducing GitHub Package Registry

GitHub introduces GitHub Package Registry, a package management service that makes it easy to publish public or private packages next to your source code.

Today, GitHub is excited to introduce GitHub Package Registry, a package management service that makes it easy to publish public or private packages next to developer’s source code.

GitHub Package Registry is fully integrated with GitHub, so users can use the same search, browsing, and management tools to find and publish packages as users do for their own repositories. Developers can also use the same user and team permissions to manage code and packages together. GitHub Package Registry provides fast, reliable downloads backed by GitHub’s global CDN. And it supports familiar package management tools: JavaScript (npm), Java (Maven), Ruby (RubyGems), .NET (NuGet), and Docker images, with more to come. GitHub Package Registry is available now in limited beta. It will always be free to use for open source—more pricing details will be announced soon.

Packages, together, with code

When developers work on a project that has dependencies on packages, it’s important for users to trust them, understand their code, and connect with the community who built them. And inside organizations, developers need to be able to quickly find what’s been approved for their use. GitHub Package Registry makes it easy to use the same familiar GitHub interface to find public packages anywhere on GitHub, or private packages within their own organization or repositories.

GitHub Package Registry is compatible with common package management clients, so developers can publish packages with their choice of tools. If the repository is more complex, developers be able to publish multiple packages of different types. And, with webhooks or with GitHub Actions, developers can fully customize the publishing and post-publishing workflows.

Most open source projects have their code on GitHub, so developers can publish prerelease versions of its packages for testing within their community, and then easily promote specific versions to the public registry of their choice.

Unified identity and permissions

Developers can now a single set of credentials across both, and manage access permissions with the same tools. Packages on GitHub inherit the visibility and permissions associated with the repository, and organizations no longer need to maintain a separate package registry and mirror permissions across systems.

Package insights

Packages hosted on GitHub include details and download statistics, along with their entire history. This makes it easy to find and use the right package as a dependency for the project, and increase user’s confidence that it only contains what’s advertised. With more insights into the packages developers publish, they can now understand exactly how other people and repositories are using them.

Sign up for the beta here:

Submit a media release