audit: compare current version to last committed version when seeing if revision should be reset #8576
+8
−1
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.
brew style
with your changes locally?brew tests
with your changes locally?#7684 refactored the logic to audit if formula version/revision numbers made sense. It compared the previous version with the newest committed version to see if the revision should have been reset. However, in the case where the last commit is a was a different version than the current formula,
previous_version
andnewest_committed_version
will be equal, even though they both differ from the current version.This change now compares the current formula version with the previous committed version to see if the revision should have be reset.
See Homebrew/homebrew-core#60536 (comment)
cc @MikeMcQuaid @SMillerDev