-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add latest tag in publishToNpm #206
Comments
Latest is the default behavior AFAIK @dblock. I believe we need an option to "NOT" tag recent release as latest? |
@gaiksaya Looks like you can use this command to tag another version as latest
Only caveat is the fact that NPM seems to tag the new version as latest by default so we might need to pass the tags (1.x vs 2.x vs latest)explicitly for every release. |
Wondering if it might be a good time to introduce something like https://stackoverflow.com/questions/68230173/publishing-a-previous-major-version-to-npm-with-no-tag-and-avoiding-latest |
I think this command right here is where we need to make sure this is actually the latest, and if not, then override the false addition of "latest" by using --tag [something_other_than+latest] as per https://docs.npmjs.com/adding-dist-tags-to-packages |
Thanks for bringing this into notice. I missed it.
https://docs.npmjs.com/cli/v9/commands/npm-dist-tag#description |
Is your feature request related to a problem? Please describe
Coming from opensearch-project/opensearch-js#521, looks like we need to npm-dist-tag as part of
publishToNpm
.Describe the solution you'd like
Mark the newly released JS component as latest in npm as part of publishing.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: