fix(release): sync release-please manifest with actually-published versions#7100
Merged
Conversation
…rsions @loopover/mcp and @loopover/miner are both live on npm at 3.1.1 (published via an out-of-band manual release cut, #7064), but .release-please-manifest.json was never updated to match -- it still recorded 3.1.0 as the last-released version for both. release-please used that stale baseline to recompute and re-propose "cut v3.1.1" as a brand-new release (#7086, #7087), which would fail on publish: npm rejects republishing an already-published version.
This was referenced Jul 17, 2026
Contributor
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
loopover-orb
Bot
added
the
gittensor:bug
This was referenced Jul 17, 2026
philluiz2323
added a commit
to philluiz2323/gittensory
that referenced
this pull request
Jul 17, 2026
… release ui:version-audit currently fails on main and closes every open contributor PR's CI (validate/validate-code): mcp-package.ts's known-latest fallback was frozen at 0.9.0 while @loopover/mcp's real npm dist-tags.latest has moved to 3.1.1 (following the release-please manifest sync in JSONbored#7100). Ran the script's own --write self-heal mode to update the literal, matching the exact fix path scripts/check-ui-mcp-version-copy.mjs documents for this drift. Also refreshed a stale "0.9.0" version number in a nearby test comment so it doesn't drift again on the next release. Included here, alongside the unrelated selfhost-env-reference change already on this branch, because no contributor PR can currently pass CI without it.
galuis116
pushed a commit
to galuis116/gittensory
that referenced
this pull request
Jul 18, 2026
…nd-editing it JSONbored#7100 fixed the immediate mismatch by hand-typing corrected version numbers into .release-please-manifest.json -- exactly the failure mode that caused the drift in the first place (a human-authored value instead of one derived from source of truth). This replaces that with a real mechanism: - scripts/sync-release-manifest.mjs treats each package's own package.json "version" as authoritative and syncs the manifest to match -- `npm run release-manifest:sync` is now the only supported way to fix drift, never a manual edit. - `npm run release-manifest:sync:check` (wired into both test:ci and .github/workflows/ci.yml, gated on backend/mcp/engine/miner/ui) fails CI the moment the manifest and a package.json disagree, instead of surfacing days later as release-please re-proposing an already-published version (JSONbored#7086/JSONbored#7087). - .release-please-manifest.json and release-please-config.json are now part of the `backend` path filter so editing either alone still triggers the check. Also corrects reference.md's CI check table, which still claimed manifest:drift-check/engine-parity:drift-check weren't wired into ci.yml -- stale since JSONbored#7067 actually added them.
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
@loopover/mcp@3.1.1and@loopover/miner@3.1.1are both live on npm (published via an out-of-band manual release cut, #7064's hand-authored release PR), but.release-please-manifest.jsonwas never updated to reflect it -- it still recorded3.1.0as each package's last-released version.release-please used that stale baseline on its next run and re-proposed "cut v3.1.1" as a brand-new release for both packages (#7086, #7087). Those would fail on publish -- npm rejects republishing an already-published version -- and are superseded by this fix; closing both.
Test plan
.release-please-manifest.jsonagainst the real, currently-published state:npm view @loopover/mcp version/npm view @loopover/miner versionboth return3.1.1, matchingpackages/loopover-mcp/package.jsonandpackages/loopover-miner/package.jsonon main.src/**change).