-
Notifications
You must be signed in to change notification settings - Fork 126
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
[Feature Request] publish using version argument #280
Comments
Yes this feature makes sense to me. I think we should just hard error if the Additionally, we'd still require specifying versions for individual packages when publishing a workspace. |
I agree that hard error in the case of |
Resolved by denoland/deno#26141. Related: #544, #555. |
Related bug: denoland/deno#27428 |
This is implemented as of #868 To use it, remove the version field from the jsr.json/deno.json and then use the Also, I'd recommend checking out https://github.com/dsherret/jsr-publish-on-tag/ |
The issue
Right now, as far as I can tell, the version of a package must be set in a config json. Be that deno.json, jsr.json or other. I miss the ability to control the version of my package outside of the package itself, specifically through a GitHub workflow that gets triggered on publishing a new release. This creates the possibility of my release version and package version being out of sync (something that I have already done by mistake).
The solution
I suggest that the publish command has a --version flag that can be optionally used to provide the new version instead of including it in the config file. I primarily want to be able to pass the exact version number, but it might also be useful to pass
patch
,minor
ormajor
to automatically increment the version.Potential issues
The text was updated successfully, but these errors were encountered: