fix(desktop): release 0.8.17 so dependabot's lockfile change reaches machines - #484
Merged
Merged
Conversation
…machines main is RED and the merge queue is stopped. Not from a code defect — from a release gate doing exactly its job. Dependabot's @types/node bump (#411) edits desktop/package-lock.json, which determines what gets BUILT into the runner. Nothing bumped desktop's version alongside it, so desktop-release-drift correctly reports "1 file changed since fleet-runner-v0.8.16, version still 0.8.16" — a change that would live on the server and on no machine at all. That is the failure the gate was written for, after six commits went missing at v0.8.12. Because the sweep only merges onto a green base, this blocked every open PR, none of which had anything to do with it. Worth naming the shape, because it will recur: a dependency bot can trip a release gate, and its PR can never carry the bump itself — the bot does not know the repo ships a desktop binary. So the bump always lands afterwards, from a human or an agent, and until it does the whole queue is stuck behind a red main. Nothing here changes behaviour; the release exists so the lockfile ships. pnpm run verify passes. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UvjGNAS9CMfEGNW26tUR4P
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.
mainis red and the merge queue is stopped. Not from a code defect — from a release gate doing exactly its job.Dependabot's
@types/nodebump (#411) editsdesktop/package-lock.json, which determines what gets built into the runner. Nothing bumped desktop's version alongside it, sodesktop-release-driftcorrectly reports:That is a change which would live on the server and on no machine at all — the exact failure the gate was written for after six commits went missing at v0.8.12.
Because the sweep only merges onto a green base, this blocked every open PR, none of which had anything to do with it. (#483 failed CI on this and not on its own diff.)
The shape, because it will recur
A dependency bot can trip a release gate, and its PR can never carry the bump itself — the bot doesn't know this repo ships a desktop binary. So the bump always has to land afterwards, from a human or an agent, and until it does the whole queue sits behind a red main.
Nothing here changes behaviour. The release exists so the lockfile ships.
Verification
npx tsx scripts/test/desktop-release-drift.ts→✓ pending — 1 file(s) changed, version 0.8.17 > released 0.8.16pnpm run verify— exit 0.🤖 Generated with Claude Code
https://claude.ai/code/session_01UvjGNAS9CMfEGNW26tUR4P