|
Hi, I try to release a package with the tag: 1.5.0-pc.7 but it gets interpreted as semver range. Do you know how I can do this? I think the version is valid, packages like next do use that format. Thanks a lot! |
Answered by
mcous
Apr 14, 2025
Replies: 1 comment 2 replies
|
Hi @m1212e, it sounds like you're confusing the concept of the released You should only use the |
2 replies
Answer selected by
m1212e
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi @m1212e, it sounds like you're confusing the concept of the released
versionwith npm's concept of distribution tags. The limitation that "distribution tags cannot match semver versions" comes from npm itself, not from this library.You should only use the
tagargument if you'd like to release a given version (e.g."version": "1.5.0-pc.7") on a "distribution tag" other than the default tag oflatest. What are the contents of your GitHub Workflow file?