feat(release): add beta publishing channel - #53
Merged
Conversation
Select a branch with a synced X.Y.Z-beta.N version and run the manual beta workflow to publish npm, PyPI, and Go prereleases without changing the public docs. Reuse the stable publishing jobs, tag npm releases as beta, and map Python package versions to PEP 440 while keeping stable releases on main.
Run manual beta releases through the npm-trusted publish workflow on main and reject any source without synchronized prerelease versions. Build source-controlled packages without credentials, then verify and publish only their artifacts in narrowly scoped jobs.
Tag a synchronized beta commit as vX.Y.Z-beta.N and push it to publish prerelease packages. Stable releases continue to publish from main. Replace the manually selected source branch and artifact handoff with an immutable tag trigger that validates the tag against .version.
Collaborator
Author
|
@codex review |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7c8369eb17
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Select a branch containing synchronized beta versions and run the Publish SDKs workflow to release it across npm, PyPI, and Go. Use the dispatch event as the beta channel signal and retain the existing main-branch push as the stable release path.
Make the empty manual trigger explicit and remove beta operations from AGENTS.md. The workflow validates its release channel at runtime.
Keep the channel check read-only without storing a version that the manual branch workflow no longer needs for tag matching.
Preserve the existing manual-trigger formatting and package-version agent guidance so the pull request stays focused on release behavior.
necolas
approved these changes
Sep 3, 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
2 participants
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.
so we can now trigger
publish.yamlas workflow through github ci, and if only our branch containsMAJOR.MINOR.PATCH-beta.NUMBERthese format of.versionfile, the workflow will deploysmth like this e.g
1.17.0-beta.1