Repository navigation
Fix release-please bootstrap-sha and cut Python 2.0.0 - #535
Merged
Seth Juarez (sethjuarez) merged 1 commit intoSep 9, 2026
Merged
Conversation
Repoint release-please bootstrap-sha to the current main tip (bc477ea) so releases are considered from the established baseline forward, and normalize the stale CHANGELOG "Unreleased" heading (was mislabeled 2.0.0-alpha.5, inconsistent with _version.py 2.0.0-beta.3). This commit is the one-time trigger to cut the first stable Python release. Only the Python runtime graduates now; the other runtimes stay on their beta line until each is independently validated. Release-As: 2.0.0 Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
This was referenced Sep 9, 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.
Why
After #534 merged, the release-please workflow ran green but opened 0 Release PRs. Root cause: the
bootstrap-shawas pinned to3c1c0cc2, which turned out to be one parent of the #534 merge commit. The branch's own commits weren't descendants of that SHA, and release-please ignores merge commits + floors atbootstrap-sha, so it sawConsidering: 0 commitsfor every runtime.What this does
bootstrap-sha3c1c0cc2→bc477ead(current main tip). This establishes a clean baseline: releases are considered from the merged state forward, so ordinaryfeat/fixcommits going forward are correctly picked up.Release-As: 2.0.0trigger commit scoped toruntime/python/prompty/. Python is the only runtime graduating now — it's the one we've actually validated this session (harness correctness, agent loop with live tool execution, Foundry provider).2.0.0-alpha.5 — Unreleased, inconsistent with_version.py's2.0.0-beta.3) to the standardUnreleasedform.Scope
x-release-please-versionannotations. They stay on their beta line and graduate individually once each is independently validated.After merge
mainand should open a Python2.0.0Release PR. Merging that PR bumps_version.py→2.0.0and cuts thepython/2.0.0tag.RELEASE_PLEASE_TOKENsecret so cut tags trigger the publish workflows. Without it, Release PRs open but publishing won't auto-fire.Co-authored-by: Copilot App 223556219+Copilot@users.noreply.github.com