Require one behavior per pull request and real-account acceptance before tagging - #144
Merged
Merged
Conversation
…ore tagging Recent patch releases bundled several behaviors with a version bump and were first exercised with real accounts only after the public installer existed, so provider-facing regressions reached users. Keep each pull request to one behavior, move the version change to its own release commit, and accept account-behavior releases with real accounts on a maintainer preview before the tag. The maintainer can waive that check. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
With the version change moved to its own release commit, a preview built from a product commit still carries the last released version. A suffix on that version sorts below the installed release, so the preview would be offered the public release as an update. Use the next patch version. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Merged
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
Between v1.0.6 and v1.0.19 most pull requests bundled several behaviors with a version bump, and real accounts first met each change in the public installer. Wake needed five pull requests across v1.0.11–v1.0.17 to get a real reply; #140 changed sign-in recovery the day after #120 closed without that flow being retested.
AGENTS.md: one independently reviewable behavior per pull request; the version changes only in a separate release commit.docs/release.md: a Real-account acceptance section. A release that changes sign-in, switching, quota, Wake, credential storage, or recovery is accepted by the maintainer on a Windows preview before the tag, with six fixed flows. The maintainer can waive it, including in the publish request.docs/release.md: the preview version now derives from the next patch version. With the version files left at the last release,<current>-rc.1sorts below the installed release.docs/testing.md: points real-account claims to that procedure.This adds a stop before tagging for account-behavior releases. It does not change the authorization for signing or publication.
Validation
Documentation only.
git diff --checkpassed.🤖 Generated with Claude Code