More descriptive error message for tag <tag> does not exist#12984
Merged
More descriptive error message for tag <tag> does not exist#12984
tag <tag> does not exist#12984Conversation
honeyankit
previously approved these changes
Aug 29, 2025
honeyankit
previously approved these changes
Aug 29, 2025
honeyankit
approved these changes
Aug 29, 2025
Member
|
I think this wording actually introduces some confusion... we shouldn't actually need to restart from the bump-versions bit, we should be okay to simply retrigger a new run of |
Merged
5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What are you trying to accomplish?
Add a more helpful error message to the
tag <tag> does not existerror we sometimes see when releasing GemsAnything you want to highlight for special attention from reviewers?
Tried to add it somewhere helpful
How will you know you've accomplished your goal?
We know what to do next time we run into this error
Checklist
N/A