fix: broken commit range due to uninitialized variable #5597
+6
−9
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.
Explanation
While running the script, I noticed the commit range was sometimes incorrect — e.g., showing
..HEAD
instead of the expectedtag..HEAD
. Turns outlatest_release_commit
was being used insidedetermine-commit-range
without being passed in, so it was empty. I fixed this by passing it explicitly as an argument.Also cleaned up a stray quote in the
USAGE
output.Checklist