chore: promote staging f9cf386 to production - #535
Merged
Merged
Conversation
release-please-config.json carried "prerelease": true and "versioning": "prerelease". Both have been in the file since at least agentex-client-v0.25.0, but nothing honoured them: the hosted generator cut python releases its own way, and 0.28.1 was cut by hand. So every python release through 0.28.1 was a normal release. 0.28.2 was the first release cut by release-please reading this file, and it did exactly what the file said -- it marked both GitHub Releases as prereleases. GitHub skips prereleases when choosing the latest release, so "latest" stayed on agentex-sdk-v0.28.1. PyPI was unaffected, since 0.28.2 is a final version string there. This target ships plain 0.x.y versions, which is what stainless.yml's `publish.release.prerelease: false` says. That setting only shapes the generated release-please workflow, though; this config is preserved from the branch rather than regenerated, so the intent never reached it. Dropping `versioning: prerelease` as well puts release-please on its default strategy. With the bump-minor-pre-major and bump-patch-for-minor-pre-major settings already here, that gives fix -> patch and feat -> minor, matching the version history. The prerelease strategy only behaves differently when the current version carries a prerelease suffix, which python's never has. The two 0.28.2 releases already created were corrected directly. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
fix(release): stop marking python releases as prereleases
aringuyen3
approved these changes
Sep 29, 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.
Automated promote from the staging trunk, opened by stlc-promote.yml.
Approve this pull request - do not click Merge. Squash and rebase both rewrite SHAs, which forks the production trunk away from staging and blocks all codegen until someone reconciles them by hand. Merge commits are disabled on this repo.
Once CI is green here and this has one approval, re-run
stlc-promote.ymlin the config repo. It fast-forwardsmainonto these exact commits, GitHub closes this pull request as merged, and the trunks stay byte-identical.This PR appears safe to merge through the stated promotion flow.
What we checked:
0.28.2, and publishing chooses a package from the unchanged tag prefix.Summary
Release configuration no longer forces prerelease versioning for automated Python releases.
Diagram
sequenceDiagram participant Main as main participant Workflow as release-please workflow participant RP as release-please participant GitHub participant Publish as publish-pypi workflow participant PyPI Main->>Workflow: Push arrives Workflow->>RP: Run release-pr with config and manifest RP->>GitHub: Open or update stable release PR Workflow->>RP: Run github-release with config and manifest alt Release PR was merged RP->>GitHub: Create component tag and published release GitHub->>Publish: Send published event Publish->>Publish: Pick package from tag prefix Publish->>PyPI: Publish package else Release PR is still open RP-->>Workflow: No release yet endReviews (1) · Last reviewed commit: "Merge pull request #9 from scaleapi/fix/..."