The newly introduced GitHub Package Registry, is package management integrated right into GitHub to allow developers to publish privately for their team, or publicly for the open source community alongside their own source code.

While GitHub Package Registry supports most other package management tools like Maven, Docker, NPM and NuGet; the multiple package types can be hosted in a single registry, devops workflow includes code and deployment solutions, coupled with APIs, and for workflow automation, GitHub Actions and webhooks.

It provide downloads backed by global CDN powering GitHub, though Packages can be hosted publicly or privately, and also used as dependencies in other projects.

The integration with GitHub will enable developers to utilize the familiar GitHub UI to work on public packages from the site or private packages within the organization.

And the full API and webhooks support, means that you can extend your workflows to work with GitHub Package Registry, and packages inherit the permissions of the repository, and no longer need third party solutions to manage and sync permissions across systems.

To start publishing your packages to GitHub, simply sign up for the beta waitlist, and be among the first to use the GitHub Package Registry. You can also check out the documentation to get a head up on what to expect.

GitHub Package Registry to enable developers to publish packages alongside source code



The newly introduced GitHub Package Registry, is package management integrated right into GitHub to allow developers to publish privately for their team, or publicly for the open source community alongside their own source code.

While GitHub Package Registry supports most other package management tools like Maven, Docker, NPM and NuGet; the multiple package types can be hosted in a single registry, devops workflow includes code and deployment solutions, coupled with APIs, and for workflow automation, GitHub Actions and webhooks.

It provide downloads backed by global CDN powering GitHub, though Packages can be hosted publicly or privately, and also used as dependencies in other projects.

The integration with GitHub will enable developers to utilize the familiar GitHub UI to work on public packages from the site or private packages within the organization.

And the full API and webhooks support, means that you can extend your workflows to work with GitHub Package Registry, and packages inherit the permissions of the repository, and no longer need third party solutions to manage and sync permissions across systems.

To start publishing your packages to GitHub, simply sign up for the beta waitlist, and be among the first to use the GitHub Package Registry. You can also check out the documentation to get a head up on what to expect.

No comments