ci(release): propose betas from master; stable only by manual dispatch - #1563
Merged
Merged
Conversation
Every push to master now runs release-please with the prerelease config, so the release PR it opens is the next vX.Y.Z-beta.N and merging it publishes a GitHub prerelease for release-beta.yml. A stable release requires dispatching release-please.yml with channel=stable and the exact version, which selects release-please-config-stable.json. The codex branch beta channel, its config, and its manifest are gone; one manifest tracks both channels.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
This was referenced Sep 17, 2026
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.
Per owner direction: no automatic stable releases for now; every release cut from
masteris a beta prerelease, and a stable release is a deliberate manual action.What changes
release-please.ymlon every push tomasterruns release-please withrelease-please-config.json, which is now the prerelease config (versioningprerelease, typebeta). The PR it opens is the nextvX.Y.Z-beta.N; merging publishes a GitHub prerelease, whichrelease-beta.ymlalready turns intotracedecay-beta-<tag>-<platform>assets.workflow_dispatchonly:gh workflow run release-please.yml --ref master -f channel=stable -f version=X.Y.Z. That selectsrelease-please-config-stable.json(the old default config, which also bumps the TypeScript SDK) and passesrelease-as. The channel step refuses stable without an exactX.Y.Z..release-please-manifest.json(set to0.1.0-beta.40, the last published tag). The codex-branch beta channel (beta-release-please.yml,release-please-config-beta.json,.release-please-manifest-beta.json) is deleted; that branch is fully merged into master and no longer a release source, so it's also dropped fromci.ymland the release-PR acceptance gate's base list.tests/release_safety_test.shnow asserts the default config proposes prereleases and the stable config publishes full releases, both draft-until-lockfile.Evidence
tests/release_safety_test.sh,tests/release_pr_integrity_test.sh,tests/release_drift_check_test.sh,scripts/test-build-mcpb.py, andactionlinton the three touched workflows all pass locally.Follow-up on merge: close #1556 (stable 0.1.0) and #1555 (codex-branch beta.41); release-please will open the beta.41 PR against master on the next push.