The GitHub Packages npm registry now runs on a new architecture, unlocking great new capabilities:
Publishing packages at organization level with GitHub Packages
Previously, npm packages published to GitHub packages were closely coupled to their repositories. Now packages can be published at an organization level. They can still be linked to a repository at any time, if needed.
Learn more about connecting a repository to a package.
Fine grained permissions for npm packages published to GitHub Packages
You can now configure Actions and Codespaces repository access on the package’s settings page, or invite other users to access the package. Additionally, npm packages published to GitHub packages can still be configured to automatically inherit all permissions from a linked repositories.
Learn more about configuring a package’s access control.
In addition to public and private, a package’s visibility can now also be set to internal. It is then visible for all members of the GitHub organization.
These new features are now available to all users on github.com.
Read more about working with the GitHub npm registry
We appreciate your feedback on these new changes in GitHub’s public community discussions!