About Registro del paquete de GitHub
Registro del paquete de GitHub is a platform for hosting and managing packages, including containers and other dependencies. Registro del paquete de GitHub combines your source code and packages in one place to provide integrated permissions management and billing, so you can centralize your software development on GitHub Enterprise Cloud.
You can integrate Registro del paquete de GitHub with GitHub APIs, GitHub Actions, and webhooks to create an end-to-end DevOps workflow that includes your code, CI, and deployment solutions.
Registro del paquete de GitHub offers different package registries for commonly used package managers, such as npm, RubyGems, Apache Maven, Gradle, Docker, and NuGet. GitHub's Registro de contenedores is optimized for containers and supports Docker and OCI images. For more information on the different package registries that Registro del paquete de GitHub supports, see "Working with a Registro del paquete de GitHub registry."
You can view a package's README, as well as metadata such as licensing, download statistics, version history, and more on GitHub Enterprise Cloud. For more information, see "Viewing packages."
Overview of package permissions and visibility
| Permissions | The permissions for a package are either inherited from the repository where the package is hosted or, for packages in the Registro de contenedores, they can be defined for specific user or organization accounts. For more information, see "Configuring a package’s access control and visibility." |
| Visibility | Puedes publicar paquetes en un repositorio público (paquetespúblicos) para compartir con todo GitHub, o en un repositorio privado (paquetes privados) para compartir con colaboradores o con una organización. |
For more information, see "About permissions for Registro del paquete de GitHub."
About billing for Registro del paquete de GitHub
El uso de Registro del paquete de GitHub es gratuito para los paquetes públicos. En el caos de los paquetes privados, cada cuenta en GitHub.com recibe cierta cantidad de almacenamiento gratuito y transferencia de datos, dependiendo de los productos que se utilicen con la cuenta. Cualquier uso que no se contemple en las cantidades incluidas se controla con los límites de gasto. Si eres un cliente que factura mensualmente, tu cuenta tendrá un límite de gastos predeterminado de 0 dólares Estadounidenses (USD), lo cual previene el uso adicional de almacenamiento o transferencia de datos después de que alcanzas las cantidades que se incluyen. Si pagas tu cuenta por factura, ésta tendrá un límite de gastos ilimitado predeterminadamente. For more information, see "About billing for Registro del paquete de GitHub."
Supported clients and formats
Registro del paquete de GitHub uses the native package tooling commands you're already familiar with to publish and install package versions.
Support for package registries
| Language | Description | Package format | Package client |
|---|---|---|---|
| JavaScript | Node package manager | package.json | npm |
| Ruby | RubyGems package manager | Gemfile | gem |
| Java | Apache Maven project management and comprehension tool | pom.xml | mvn |
| Java | Gradle build automation tool for Java | build.gradle or build.gradle.kts | gradle |
| .NET | NuGet package management for .NET | nupkg | dotnet CLI |
| N/A | Docker container management | Dockerfile | Docker |
For more information about configuring your package client for use with Registro del paquete de GitHub, see "Working with a Registro del paquete de GitHub registry."
For more information about Docker and the Registro de contenedores, see "Working with the Container registry."
Authenticating to Registro del paquete de GitHub
You need an access token to publish, install, and delete packages.
You can use a personal access token (PAT) to authenticate to Registro del paquete de GitHub or the GitHub API. When you create a personal access token, you can assign the token different scopes depending on your needs. For more information about packages-related scopes for a PAT, see "About permissions for GitHub Packages."
To authenticate to a Registro del paquete de GitHub registry within a GitHub Actions workflow, you can use:
GITHUB_TOKENto publish packages associated with the workflow repository.- a PAT to install packages associated with other private repositories (which
GITHUB_TOKENcan't access).
Para obtener más información sobre el GITHUB_TOKEN que se utiliza en los flujos de trabajo de GitHub Actions, consulta la sección "Autenticarse en un flujo de trabajo".
Managing packages
You can delete a package in the GitHub.com user interface or using the REST API. For more information, see the "Registro del paquete de GitHub API."
When you use the GraphQL API to query and delete private packages, you must use the same token you use to authenticate to Registro del paquete de GitHub. For more information, see "Deleting and restoring a package" and "Forming calls with GraphQL."
You can configure webhooks to subscribe to package-related events, such as when a package is published or updated. For more information, see the "package webhook event."
Contacting support
If you have feedback or feature requests for Registro del paquete de GitHub, use a Registro del paquete de GitHub feedback discussion.
Contact Soporte de GitHub about Registro del paquete de GitHub using our contact form if:
- You experience anything that contradicts the documentation
- You encounter vague or unclear errors
- Your published package contains sensitive data, such as GDPR violations, API Keys, or personally identifying information