How to tag package version in github packages registry?

[mrspd]

Hello. I try publish npm package with specific tag, but package always tagged as "latest". Is there a way to publish package with another tag or disable "latest" autotagging?

[20481A05K0]

@mrspd
Yes, you can publish an npm package with a specific tag using the npm publish command with the --tag option. This allows you to specify a custom tag for your package version, overriding the default behavior of tagging it as "latest".

Example:
If you want to tag the package version as "beta", you would use:

npm publish --tag beta

[mrspd]

It's not work with GitHub registry

[imDarshanGK]

Hi @mrspd,

• In your package.json, add:

"publishConfig": {
"registry": "GitHub registry URL"
}

• Publish with a tag like beta:

npm publish --tag beta

[mrspd]

Is it necessary, publishConfig in package.json? I publishing from GitHub action and use setup-node action with registry url.

[imDarshanGK]

Hi @mrspd,

No, it's not strictly necessary to add publishConfig in package.json if you're already setting the registry URL in the GitHub Action using setup-node. You can publish directly with a tag using the following command in your GitHub Actions workflow:

• name: Publish Package
  run: npm publish --tag beta
  env:
  NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

As long as your GitHub Actions workflow is set up with the correct registry URL, this should work without needing the publishConfig in package.json.

[mrspd]

I was try the same code before writing this post 🥲 Is there an example repository where I can see other tag, but not "latest"?

[imDarshanGK]

Hi @mrspd,

• Ensure that setup-node is properly configured in your workflow.

• Use this command to publish with the tag:

  • run: npm publish --tag beta
    env:
    NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

• This will publish the package with the beta tag instead of latest. If it's still not working, check your token and ensure you're correctly authenticating with GitHub.

[mrspd]

Yep, I was wrong. npm publish work properly. But on github site you could see "latest" tag label only. If you want watch all tags, use npm dist-tag ls.