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
Question:
I want to display an output that the version is about to be upgraded before running the nbgv prepare-release command.
In order to display it, I need to get somehow the next future version, which for example depends on the version increment being set in the version.json file. Is there a way to get the version that nbgv prepare-release will set in a simulative manner?
The text was updated successfully, but these errors were encountered:
No.
What if we added a --what-if switch, which prints the new version but doesn't actually make any changes?
Do you need the output to be machine-readable, or merely human readable?
Great. We'll keep this issue active in case you or others can prepare the PR.
Sponsorship may be an effective way to lead a contributor of this repo to prioritize the feature. As a free and open source library, all or the majority of its development is done without any monetary benefit to its authors, and all of it is made available free of charge. But sponsorship is very much appreciated and, with agreement from a particular contributor and/or the owning team, can be a great way to support the project and help get your favorite features or bugs addressed in an upcoming version.
If sponsorship to drive completion of a feature or bug fix is an interesting option to you, please let us know. You can reach out to me privately on keybase.io or gitter.im as well.
Question:
I want to display an output that the version is about to be upgraded before running the
nbgv prepare-release
command.In order to display it, I need to get somehow the next future version, which for example depends on the version increment being set in the
version.json
file. Is there a way to get the version thatnbgv prepare-release
will set in a simulative manner?The text was updated successfully, but these errors were encountered: