fix(ci): grace-window the MCP known-latest audit so same-day releases stop redding every branch#8179
Merged
Merged
Conversation
… stop redding every branch Three times in one night (3.4.0, 3.5.0, 3.6.0) a fresh @loopover/mcp publish turned ui:version-audit red for main and every in-flight branch/gate -- a mismatch that is neither the branch's fault nor actionable from it, while the scheduled sync PR (the real fix) lands within minutes anyway. The audit now reads the latest version's publish time from the same registry response: a mismatch within 24h of publish emits a ::warning and passes (the sync PR is the fix); older than that is genuine staleness and still hard-fails -- preserving the #3047 anti-drift discipline. Offline/env-override enforcement (LOOPOVER_MCP_LATEST_VERSION, no publish time available) deliberately stays strict, and --write self-healing is unchanged.
Contributor
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #8179 +/- ##
=======================================
Coverage 92.06% 92.06%
=======================================
Files 768 768
Lines 77838 77838
Branches 23517 23517
=======================================
Hits 71663 71663
Misses 5062 5062
Partials 1113 1113
Flags with carried forward coverage won't be shown. Click here to find out more. |
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
1 participant
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.
Root-cause fix for tonight's recurring red cascades (3.4.0 → 3.5.0 → 3.6.0, each one turning
ui:version-auditred repo-wide until a sync PR + rebases): the audit now reads the latest version's publish time from the same registry response and treats a mismatch within 24h of publish as a::warning(the scheduled sync PR is the fix), while anything older remains a hard failure — the #3047 anti-staleness discipline is fully preserved, and offline enforcement viaLOOPOVER_MCP_LATEST_VERSIONdeliberately stays strict. Verified live against the current 3.5.0-vs-3.6.0 mismatch: warns and passes. Pure helper + both boundary arms + strict-fallback arms tested.Merging #8178 (the 3.6.0 sync) is still right — this just stops the next release evening from redding every open branch. Complements #8173.