-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
chore: publish 1.x NPM packages with the v1 tag #11188
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
Conversation
v2 stable is knocking, and it'll be the `latest` tag release soon, so the 1.x ones should have their own tag `v1`
Package Changes Through ebbe017No changes. Add a change file through the GitHub UI by following this link. Read about change files or the docs at github.com/jbolda/covector |
| run: | | ||
| echo "//registry.npmjs.org/:_authToken=$NPM_TOKEN" >> ~/.npmrc | ||
| npm publish | ||
| npm publish --tag v1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we really need a tag? Isn't this the same as just using @1 ?
For me, tags have always been just a way to change between stable and next (alpha, beta or rc)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmm you do have a point, i guess we just need to change docs then cc @tweidinger
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks like this works tauri-apps/tauri-docs#2773
v2 stable is knocking, and it'll be the
latesttag release soon, so the 1.x ones should have their own tagv1