You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(ci): grace-window the MCP known-latest audit so same-day releases stop redding every branch (#8179)
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.
`${SOURCE_LATEST_PATH}: known latest ${sourceLatest} does not match npm dist-tags.latest ${latest} (published ${latestPublishedAt??"unknown"}, beyond the ${KNOWN_LATEST_GRACE_WINDOW_MS/3_600_000}h grace window)`,
87
+
);
62
88
}else{
63
-
failures.push(`${SOURCE_LATEST_PATH}: known latest ${sourceLatest} does not match npm dist-tags.latest ${latest}`);
89
+
console.warn(
90
+
`::warning::${SOURCE_LATEST_PATH}: known latest ${sourceLatest} is behind npm dist-tags.latest ${latest}, published within the grace window -- the scheduled sync PR is the fix; not failing this build`,
91
+
);
64
92
}
65
93
}elseif(!latest){
66
94
console.warn(
@@ -177,7 +205,7 @@ export function readMinimumSupportedVersion(path: string): string {
0 commit comments