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

Warnings are hard to separate from desired output #254

Closed
mdellweg opened this issue Nov 14, 2024 · 0 comments · Fixed by #264
Closed

Warnings are hard to separate from desired output #254

mdellweg opened this issue Nov 14, 2024 · 0 comments · Fixed by #264
Labels
feature-request New feature or request good first issue Good for newcomers

Comments

@mdellweg
Copy link

  • bump-my-version version: 0.28.1
  • Python version: 3.12.7
  • Operating System: Linux

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

$ 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.

@coordt coordt added feature-request New feature or request good first issue Good for newcomers labels Nov 14, 2024
@coordt coordt linked a pull request Dec 14, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request New feature or request good first issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants