[ad_1]
GitHub announced today the launch of a limited beta version of GitHub Package Registry, its new package management service that allows developers to publish public and private packages next to their source code.
To be clear, GitHub does not run a competitor for tools like npm or RubyGems. What the company launches, however, is a service that is compatible with these tools and allows developers to find and publish their own packages, using the same GitHub interface used for their code. The new service is currently compatible with JavaScript (npm), Java (Maven), Ruby (RubyGems), .NET (NuGet) and Docker images, with support for other languages and tools to come.
"GitHub The package register is compatible with current package management clients. So you can publish packages with the tools you want, "says Simina Pasat, Director of Product Management at GitHub. "If your repository is more complex, you will be able to publish several packages of different types. And with Web hooks or with GitHub Actions, you can fully customize your publishing and post-publishing workflows. "
With this, companies can also provide their employees with a single set of credentials to manage both their code and their packages. This new feature also makes it easier to create a set of trusted packages. Users will also receive download statistics and access the full history of the package on GitHub.
Most open-source packages already use GitHub to develop their code before publishing it to a public registry. GitHub claims that these developers can now use the GitHub package registry to publish preliminary versions, for example.
Developers already often use GitHub to host their private repositories. After all, it makes sense to keep packages and code in one place. What GitHub does here, to a certain extent, is to formalize this practice and wrap a product around it.
[ad_2]
Source link