fix(ui): sync MCP_PACKAGE_KNOWN_LATEST_VERSION with npm dist-tags.latest - #7115
Merged
Conversation
Stale since @loopover/mcp published 3.1.1 -- ui:version-audit (already CI-enforced) caught the drift; this is the mechanical `npm run ui:version-audit:sync` fix.
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
loopover-ui | eb88601 | Commit Preview URL Branch Preview URL |
Jul 17 2026, 09:55 PM |
Contributor
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
loopover-orb
Bot
added
the
gittensor:bug
Bundle ReportBundle size has no change ✅ Affected Assets, Files, and Routes:view changes for bundle: loopover-uiAssets Changed:
|
This was referenced Jul 17, 2026
galuis116
pushed a commit
to galuis116/gittensory
that referenced
this pull request
Jul 18, 2026
Stale again since @loopover/mcp published 3.2.1 (this exact class of drift already hit and got fixed once this session, JSONbored#7115) -- blocked an unrelated auto-generated release PR's (JSONbored#7133) CI. The durable fix (auto-sync this after every mcp publish, instead of a human noticing red CI on an unrelated PR) is a separate follow-up.
galuis116
pushed a commit
to galuis116/gittensory
that referenced
this pull request
Jul 18, 2026
…lish apps/loopover-ui/src/lib/mcp-package.ts's MCP_PACKAGE_KNOWN_LATEST_VERSION (ui:version-audit, already CI-enforced) goes stale the moment mcp publishes a new version -- and since nothing updated it automatically, that showed up as a completely unrelated PR's CI turning red with zero connection to what it actually changed (confirmed live: an auto-generated release PR for a DIFFERENT package hit this exact gap twice in one session, JSONbored#7115 and JSONbored#7134). Can't be pre-synced in the Release PR itself: the value must never claim a version ahead of what's actually on npm (the check's own header comment already establishes this), so the earliest correct moment to update it is right after publish succeeds. Opens a small PR instead of pushing to main directly, since this repo's branch protection requires PRs.
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.
Summary
apps/loopover-ui/src/lib/mcp-package.ts'sMCP_PACKAGE_KNOWN_LATEST_VERSIONwas still"0.9.0", stale since@loopover/mcppublished3.1.1.ui:version-audit(already CI-enforced, not a new check) caught it:known latest 0.9.0 does not match npm dist-tags.latest 3.1.1. Mechanical fix via the existingnpm run ui:version-audit:sync.Test plan
npm run ui:version-audit-- clean after the fixnpm run ui:test-- 261/261 tests pass (one unrelated fresh-worktree failure from a not-yet-built@loopover/enginedist, resolved bynpm run build --workspace @loopover/engine, not a real regression)