fix(version): resync server.json/package.json to the released 0.1.2 - #10
Merged
Conversation
server.json and packages/gotify-rmcp/package.json were hand-bumped to 0.1.3 in b096afa ("chore: publish MCP Registry metadata") on 2026-07-12. No 0.1.3 was ever released: there is no v0.1.3 tag, Cargo.toml is 0.1.2, and .release-please-manifest.json is 0.1.2. The repo's real version is 0.1.2, so bring those two files back to it. The drift survived because this repo carried an 87-line variant of check-version-sync.sh that never looks at server.json — it reported "OK — all 1 files at v0.1.2" while server.json sat at 0.1.3. Replace it with the 97-line variant already used by synapse and rarcane, which checks all four version-bearing files; it now reports 4 and fails on injected drift (verified). Wire it into npm-package.yml, which runs on pull_request and on push to main, so this cannot drift silently again. rapprise is the only repo in the fleet that already gated this in CI.
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.
Unblocks the stale release PR #4.
server.jsonandpackages/gotify-rmcp/package.jsonwere hand-bumped to 0.1.3 inb096afa(2026-07-12). No 0.1.3 was ever released — there is nov0.1.3tag,Cargo.tomlis 0.1.2, and.release-please-manifest.jsonis 0.1.2. The repo's real version is 0.1.2, so those two files come back to it.Why it went unnoticed: this repo carried an 87-line variant of
check-version-sync.shthat never looks atserver.json. It reportedOK — all 1 files at v0.1.2while server.json sat at 0.1.3. The script is forked into 4 variants across the fleet:Replaced with the 97-line variant — it now reports 4 files and fails on injected drift (verified with a negative control). Wired into
npm-package.yml, which runs onpull_requestand push tomain.Note rtailscale and runifi carry the same blind 87-line script and should get the same treatment.