Note: Paquetes de GitHub is currently in beta for Servidor de GitHub Enterprise 2.22. To join the beta for your instance, use the sign-up form.
About Paquetes de GitHub
Paquetes de GitHub is a platform for hosting and managing packages, including containers and other dependencies. Paquetes 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.
You can integrate Paquetes de GitHub with GitHub Enterprise APIs, GitHub Actions, and webhooks to create an end-to-end DevOps workflow that includes your code, CI, and deployment solutions.
Paquetes de GitHub offers different package registries for commonly used packages, such as for Node, RubyGems, Apache Maven, Gradle, and Nuget.
Viewing packages
You can review the package's README, some metadata like licensing, download statistics, version history, and more on GitHub Enterprise. For more information, see "Viewing packages."
About package permissions and visibility
| Package registries | |
|---|---|
| Hosting locations | You can host multiple packages in one repository. |
| Permissions | Each package inherits the permissions of the repository where the package is hosted. For example, anyone with read permissions for a repository can install a package as a dependency in a project, and anyone with write permissions can publish a new package version. |
| Visibility | Puedes publicar paquetes en un repositorio público (paquetes públicos) para compartir con todo GitHub, o en un repositorio privado (paquetes privados) para compartirlos con colaboradores o con una organización. |
Supported clients and formats
Paquetes 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 Paquetes de GitHub, see "Package client guides for Paquetes de GitHub."
Authenticating to Paquetes de GitHub
Necesitas de un token de acceso para publicar, instalar, y borrar paquetes en Paquetes de GitHub. Puedes utilizar un token de acceso personal para autenticarte con tu nombre de usuario directamente en Paquetes de GitHub o en la API de GitHub. Cuando creas un token de acceso personal, puedes asignar al token diferentes ámbitos en función de tus necesidades.
To authenticate to Paquetes de GitHub using a GitHub Actions workflow, you must use GITHUB_TOKEN.
About scopes and permissions for package registries
To use or manage a package hosted by a package registry, you must use a token with the appropriate scope, and your user account must have appropriate permissions for that repository.
For example:
- To download and install packages from a repository, your token must have the
read:packagesscope, and your user account must have read permissions for the repository. - To delete a specified version of a private package on GitHub Enterprise, your token must have the
delete:packagesandreposcope. Public packages cannot be deleted. For more information, see "Deleting a package."
| Scope | Description | Repository permissions |
|---|---|---|
read:packages | Download and install packages from Paquetes de GitHub | read |
write:packages | Upload and publish packages to Paquetes de GitHub | write |
delete:packages | Delete specified versions of private packages from Paquetes de GitHub | admin |
repo | Upload and delete packages (along with write:packages, or delete:packages) | write, or admin |
When you create a GitHub Actions workflow, you can use the GITHUB_TOKEN to publish and install packages in Paquetes de GitHub without needing to store and manage a personal access token.
For more information, see:
- "Using Paquetes de GitHub with GitHub Actions"
- "Creating a personal access token"
- "Available scopes"
Managing packages
You can delete a version of a private package in the GitHub Enterprise user interface or using the GraphQL API.
When you use the GraphQL API to query and delete private packages, you must use the same token you use to authenticate to Paquetes de GitHub. For more information, see "Deleting 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 need support for Paquetes de GitHub, please contact your site administrators.