Revert "feat(ci): auto-bump recall floors after stable releases" (#2162) - #2166
Merged
Conversation
This reverts commit 8f9f9d8.
Contributor
Greptile SummaryReverts the recall-floor auto-update feature:
Confidence Score: 5/5The revert appears safe to merge with no actionable issues identified. The deleted workflow and script were self-contained additions, and no remaining repository callers or configuration depend on either file. Important Files Changed
Reviews (1): Last reviewed commit: "Revert "feat(ci): auto-bump recall floor..." | Re-trigger Greptile |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
Reverts #2162. That PR was merged without checking Greptile's review — it has a Confidence Score of 2/5 with 3 real, unaddressed findings:
workflow_dispatchretry finishing after a newer release tag exists would mislabel and force-push older benchmark metrics onto the newer release's branch.This PR only reverts; it does not merge itself. A follow-up PR fixing all three issues will be opened separately once ready.