Innovation Awards 2022 is the market-leading awards program for celebrating ecosystem innovation and excellence across the technology sector in ASEAN.
- 15 May 2019 13:07
Introducing GitHub Package Registry
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.
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.
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: https://github.com/features/package-registry/signup