Uh oh!
There was an error while loading. Please reload this page.
chore: bump the version in every PR, and make that possible - #33
Merged
Conversation
A running instance replaces itself only when the binary's version differs from the one it registered, so merging a behaviour change without a bump leaves every open instance on the old build until someone restarts it by hand. Two merges have gone in that way. `scripts/release.ts` could not be used inside a branch: it commits and tags, and develop takes squash merges, so the commit is rewritten and the tag is left pointing at a commit that never lands. `--no-git` writes the versions and stops there. v0.9.7, which is this rule applied to the pull request that adds it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018PkYQzbsnMihHesafWvXKs
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 freeto 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.
A running instance replaces itself only when the binary version differs from the one it registered (
isStaleinpackages/cli/src/index.ts). So a merge without a bump leaves every instance that is already open serving the old build, silently. #31 and #32 both went in that way — six instances here are still on 0.9.6.Three things:
AGENTS.mdwith the rule. It is the first agent-facing doc in the repo.--no-gitonscripts/release.ts, without which the rule cannot be followed: the script commits and tags, and since develop takes squash merges the commit is rewritten on the way in and the tag is left pointing at a commit that never lands. Default behaviour is unchanged.parser 43, git 44, github 21, ui 371, cli 157; the built binary reports 0.9.7.
🤖 Generated with Claude Code
https://claude.ai/code/session_018PkYQzbsnMihHesafWvXKs