release: 5.3.0 - #16
Closed
stainless-app[bot] wants to merge 6 commits into
Closed
Conversation
Replace the hosted-Stainless release step with community googleapis/release-please-action@v4, running on push to `next` (the branch generation lands on). Requires a RELEASE_PLEASE_TOKEN PAT secret (Contents:RW + PRs:RW) — the default GITHUB_TOKEN cannot trigger publish-pypi.yml's release:published event. Also widen release-doctor's PR trigger to include `next` since release PRs now target it instead of `main`. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WLJNWZ5H1JM4ffk32S8bg3
Adds concurrency (group: release-please-next, no cancel-in-progress) so overlapping pushes to next from the generator's regen+stamp commits can't race release-please into a stale-version state. After a release is actually created, fast-forwards main to the released next commit using RELEASE_PLEASE_TOKEN (never a force-push: a non-fast-forward push is rejected, not overwritten). Also drops "versioning": "prerelease" / "prerelease": true from release-please-config.json — that combination only made sense for the old Stainless-fork pipeline. Confirmed from release-please source (versioning-strategies/default.ts and prerelease.ts) that both strategies check the same Release-As commit note identically before computing any bump, so removing them preserves Release-As overrides and yields clean major.minor.patch bumps for normal commits. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WLJNWZ5H1JM4ffk32S8bg3
ci: self-hosted release-please on next
Stainless-Generated-From: 1c03533
Release-As: 5.2.1
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
August 20, 2026 09:43
9b995d7 to
392973e
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
August 20, 2026 09:43
392973e to
4acfcb9
Compare
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 Release PR
5.2.1 (2026-08-20)
Full Changelog: v5.2.0...v5.2.1
Features
Bug Fixes
This pull request is managed by Stainless's GitHub App.
The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.
For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.
🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions