Skip to content

feat: migrate SDK release automation to release-please (off Stainless)#97

Merged
aburkard merged 1 commit into
mainfrom
rp-nd
Jun 26, 2026
Merged

feat: migrate SDK release automation to release-please (off Stainless)#97
aburkard merged 1 commit into
mainfrom
rp-nd

Conversation

@aburkard

Copy link
Copy Markdown
Contributor

Adds our in-house release-please workflow (uses the PRODUCTION_REPO_TOKEN org secret), replacing Stainless's external release automation. First release cut by this workflow will be 0.40.0 (SDK content already promoted to main). Part of the ENG-2597 Stainless cutover.

Adds the in-house release-please workflow that opens/maintains the release PR and
tags on merge, using PRODUCTION_REPO_TOKEN. Replaces the release automation that
Stainless ran externally via the stainless-app GitHub App (being retired). The
SDK content was already promoted from staging.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@firetiger-agent

firetiger-agent Bot commented Jun 26, 2026

Copy link
Copy Markdown

Firetiger has created a monitoring plan for this PR.

View monitor

@aburkard aburkard merged commit 4220668 into main Jun 26, 2026
8 checks passed
@aburkard aburkard mentioned this pull request Jun 26, 2026
@entelligence-ai-pr-reviews

Copy link
Copy Markdown

Confidence Score: 5/5 - Safe to Merge

Safe to merge — this PR migrates the SDK release automation from Stainless to release-please, a well-established Google-maintained release tooling system. The change is purely in CI/CD automation infrastructure and introduces no runtime code changes that could affect SDK behavior or consumers. No issues were identified during automated review across the changed files.

Key Findings:

  • The migration from Stainless to release-please is a straightforward tooling substitution with no impact on the SDK's actual source code, API surface, or runtime behavior.
  • Release-please is a battle-tested, widely adopted release automation tool that follows conventional commits to manage changelogs and versioning, making this a positive improvement in release process transparency and standardization.
  • Zero review comments were generated and no pre-existing unresolved issues were flagged, indicating the implementation is clean and follows expected patterns for release automation configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant