Skip to content
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

Release 6.0.0-beta #543

Merged
merged 1 commit into from
Aug 20, 2024
Merged

Release 6.0.0-beta #543

merged 1 commit into from
Aug 20, 2024

Conversation

ExplodingCabbage
Copy link
Collaborator

No description provided.

@ExplodingCabbage ExplodingCabbage merged commit 3b1ac53 into master Aug 20, 2024
@ExplodingCabbage ExplodingCabbage deleted the 6.0.0-beta branch August 20, 2024 16:49
@silverwind
Copy link

silverwind commented Aug 20, 2024

FYI, This beta was published as dist-tag latest which means npm install diff will install the beta, which may be unexpected. It's better to publish betas under their own dist-tag, like beta.

@ExplodingCabbage
Copy link
Collaborator Author

Oh, man! Thanks for letting me know; it's my first time helping maintain an npm package and I hadn't really noticed tags were a thing nor realised they'd affect npm install behaviour. (I wrongly assumed it was semver-aware and wouldn't install a pre-release version unless explicitly asked to; I should've checked with a test package.)

@silverwind
Copy link

It's a common misunderstanding with npm, I've seen it too many times. To fix, you could publish the v6 beta again using npm publish --tag beta and then publish another v5 release without the --tag argument.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants