Repository navigation
ci(release): scope release-please to Python for first GA - #536
Merged
Seth Juarez (sethjuarez) merged 1 commit intoSep 9, 2026
Merged
Conversation
The previous run crashed with "is not a package manifest (might be a cargo workspace)" on runtime/rust/Cargo.toml, aborting the entire run before any Release PR was created. It was also trying to release the typescript and rust backlogs (2.1.0-beta) off their existing beta tags, which we don't want until each runtime is independently validated. Scope release-please to the python component only for the first GA. The other six components (rust, typescript, csharp, java, go, swift) and the node-workspace plugin are preserved in git history and will be re-added one PR at a time as each runtime is validated. The rust re-add must point at member manifests, not the workspace root Cargo.toml. The already-merged feat(python) Release-As: 2.0.0 commit stays in range, so python still graduates to exactly 2.0.0. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
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.
Why
After #535 merged, the release-please run crashed:
The
rustcomponent pointed atruntime/rust/Cargo.toml, which is a workspace manifest, not a package manifest. release-please's rust updater can't parse it, and the error aborts the entire run before any Release PR is created — so it took the Python release down with it.The run was also computing backlog releases for typescript → 2.1.0-beta.5 and rust → 2.1.0-beta.4 off their existing beta tags — runtimes we haven't validated yet.
What this does
Scopes release-please to the Python component only for the first GA. This:
feat(python): … Release-As: 2.0.0commit (still in range afterbootstrap-sha) open a clean Python2.0.0Release PR.Not lost — deferred
The other six components (rust, typescript, csharp, java, go, swift) and the
node-workspaceplugin are preserved in git history (see #534). They'll be re-added one PR at a time as each runtime is validated — a natural checkpoint to actually verify each before it can cut a release. The rust re-add must point at the member manifests (runtime/rust/prompty,runtime/rust/prompty-openai, …), not the workspace root.After merge
release-please runs on the push to
mainand should open a single Python2.0.0Release PR (rewrites_version.py→2.0.0, bumps the manifest, adds the CHANGELOG section).Co-authored-by: Copilot App 223556219+Copilot@users.noreply.github.com