You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running bump-my-version show new_version --increment release is supposed to output the new version in a parsable form. But in the face of a warning, the output is hard to dissect by a script. If the warning could be suppressed or routed to stderr, this would be easy to accomplish. The specific command I am interested in is: NEW_VERSION="$(bump-my-version show new_version --increment release)"
What I Did
$ NEW_VERSION="$(bump-my-version show new_version --increment release)"
$ echo"$NEW_VERSION"
WARNING:
The .cfg file format is deprecated. Please use .toml instead.
3.68.0
My suggestion would be to add err=True to the call to click.secho in print_warning.
The text was updated successfully, but these errors were encountered:
Description
Running
bump-my-version show new_version --increment release
is supposed to output the new version in a parsable form. But in the face of a warning, the output is hard to dissect by a script. If the warning could be suppressed or routed to stderr, this would be easy to accomplish. The specific command I am interested in is:NEW_VERSION="$(bump-my-version show new_version --increment release)"
What I Did
My suggestion would be to add
err=True
to the call toclick.secho
inprint_warning
.The text was updated successfully, but these errors were encountered: