May 12, 2019 at 15:00Presented by GitHub Package Registry
- Transfer
GitHub Package Registry, a package management service that makes it easy to publish public or private packages near source, has been released.
The GitHub package registry is fully integrated with GitHub, so you can use the same search, view, and control tools to find and publish packages as you would with repositories. You can also use the same user and team rights to jointly manage code and packages. The GitHub Package Registry provides fast and reliable downloads, with support for the global GitHub CDN. In addition, it supports the familiar package management tools: JavaScript (npm), Java (Maven), Ruby (RubyGems), .NET (NuGet) and Docker (and others on the way).
You can try the GitHub Package Registry today in a limited beta. It will always be free to use for Open-Source. More pricing information will be announced shortly.
Try Beta
When you are working on a project that depends on packages, it is important that you trust them, understand their code and communicate with the community that created them. And within organizations, you should be able to quickly find what has been approved for your use. The GitHub package registry makes it easy to use the same familiar GitHub interface to search for public packages anywhere on GitHub or private packages in your organization or repositories.
The GitHub package registry is compatible with regular package management clients, so you can publish packages using the tools you choose. If your repository is more complex, you can publish several packages of different types. And with webhooks or with GitHub Actions, you can fully customize your publishing and post-publishing workflows.
Publishing an Open Source Package? Most open source projects have their own code on GitHub, so you can publish preview versions of your packages for testing in your community, and then easily add specific versions to the open registry of your choice.
If you use different systems for your code and packages today, you have to maintain different sets of credentials and user permissions. Now you can use one set of credentials for both and manage access permissions using the same tools. GitHub packages inherit the visibility and permissions associated with the repository, and organizations no longer need to maintain a separate package registry and mirror permissions for different systems.
The packages hosted on GitHub contain detailed information and download statistics, as well as their entire history, so you know exactly everything about them. This makes it easier to find and use the right package as a dependency for your project and increases your confidence that it contains only what you need. By receiving more information about the packages you publish, you can understand exactly how other people and repositories use them.
The GitHub package registry is currently in beta.
Register to start
The GitHub package registry is fully integrated with GitHub, so you can use the same search, view, and control tools to find and publish packages as you would with repositories. You can also use the same user and team rights to jointly manage code and packages. The GitHub Package Registry provides fast and reliable downloads, with support for the global GitHub CDN. In addition, it supports the familiar package management tools: JavaScript (npm), Java (Maven), Ruby (RubyGems), .NET (NuGet) and Docker (and others on the way).
You can try the GitHub Package Registry today in a limited beta. It will always be free to use for Open-Source. More pricing information will be announced shortly.
Try Beta
Packages with your code
When you are working on a project that depends on packages, it is important that you trust them, understand their code and communicate with the community that created them. And within organizations, you should be able to quickly find what has been approved for your use. The GitHub package registry makes it easy to use the same familiar GitHub interface to search for public packages anywhere on GitHub or private packages in your organization or repositories.
The GitHub package registry is compatible with regular package management clients, so you can publish packages using the tools you choose. If your repository is more complex, you can publish several packages of different types. And with webhooks or with GitHub Actions, you can fully customize your publishing and post-publishing workflows.
Publishing an Open Source Package? Most open source projects have their own code on GitHub, so you can publish preview versions of your packages for testing in your community, and then easily add specific versions to the open registry of your choice.
Unified Authentication and Permissions
If you use different systems for your code and packages today, you have to maintain different sets of credentials and user permissions. Now you can use one set of credentials for both and manage access permissions using the same tools. GitHub packages inherit the visibility and permissions associated with the repository, and organizations no longer need to maintain a separate package registry and mirror permissions for different systems.
Insiders about the package
The packages hosted on GitHub contain detailed information and download statistics, as well as their entire history, so you know exactly everything about them. This makes it easier to find and use the right package as a dependency for your project and increases your confidence that it contains only what you need. By receiving more information about the packages you publish, you can understand exactly how other people and repositories use them.
Join beta
The GitHub package registry is currently in beta.
Register to start