release: add dev promotion flow - #20
Merged
Merged
Conversation
gcharang
added a commit
that referenced
this pull request
Jul 28, 2026
The custom domain shipped and the first `*/15` tick after Metamind b70c40e went live cleared every stale lease — including the one that had carried `cleanup failed (404)` in its durable last_error for six hours. `released` requires a confirmed 204, so those transitions are themselves the proof that the sweep's subrequest now arrives. Also records the ordering that mattered: PR #20 carried both the routing fix and the fix for the sweep tearing a session down mid-attach. Merging the routing fix first would have had the first tick destroy live sessions instead of dead ones.
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
devas the integration branch for feature, fix, and Version Packages pull requests.devfrom publishing onmaster.mastercommit if it still contains a pending changeset.masterremains the default release branch. Its repository rules now match Anchorage: pull requests are required, and deletion and force-pushes are blocked.User impact
Package APIs and runtime behavior do not change. Maintainers merge ordinary work into
dev, merge the generated Version Packages pull request intodev, then promote that versioned commit tomaster.Verification
git diff --checkyq eval '.' .github/workflows/ci.yml .github/workflows/version.yml .github/workflows/release.ymlpnpm install --frozen-lockfilepnpm changeset statuspnpm --filter "./packages/*" buildpnpm -r typecheckpnpm -r testpnpm -r buildThe pre-cutover release published
@understudy/protocol@0.8.0and@understudy/connector@0.5.1. npm, git tags, GitHub Releases, and the release commit CI all passed.No changeset is included because this changes repository operations and documentation, not a published package.