Package Registries

Package registry integrations give codev's workflows authenticated access to a private npm registry, so builds and pipelines can install (and publish) private packages without committing tokens to your repository. codev stores the credential and generates an authenticated .npmrc on demand at run time.

Choose a provider

GitHub Packages needs no separate registry integration — its authentication is drawn from your GitHub source-control integration.

Which registry codev uses

When more than one registry is configured, codev chooses by the default flag first, then by type in the order GitHub Packages → JFrog → npm → GitLab. To switch the active registry, mark a different integration as the default for the artifact-registry category. See npm Registry for the full explanation.