-
-
Notifications
You must be signed in to change notification settings - Fork 306
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
Support hatch version --force
#1645
Conversation
Thanks! I pushed a commit to use a slightly different approach in the backend. Rather than a CLI option for Hatchling, I'm using an environment variable as I recommended in a similar change: #1511 (comment) The benefit is that if the backend happens to be a version before the introduction of the CLI option then nothing would break. |
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.
Thanks a lot, good feature!
Co-authored-by: Ofek Lev <[email protected]> e07d298
Co-authored-by: Ofek Lev <[email protected]> e07d298
Thanks, this makes sense! I'll keep that in mind for the future. Question: are these environment variables documented? |
The other one I mentioned is not because the PR is still open and waiting for the recommendation. However, you're right that I forgot to document this outside of the plugin property! If you have time, it should be documented here as well. Otherwise, I will make sure to do this before the next release! |
Co-authored-by: Ofek Lev <[email protected]> e07d298
When downgrading with an explicit version number, normally
hatch
will raise an error. Whilevalidate-bump
can be provided in the config file, it's useful to be able to override this check on the command line. This PR implementshatch version --force <downgrade-version>
.Closes: #1458