Skip to content

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

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

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

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.39.0 (the SDK content already landed via #113). 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 in #113.

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 bf89680 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-understood and widely-adopted release tooling solution. The review generated zero comments, no logic issues, no security concerns, and no correctness problems were identified across the changed files. The migration is a build/CI infrastructure change that improves release automation standardization without touching runtime SDK code.

Key Findings:

  • No issues were identified in the automated review — zero critical, significant, or medium-severity findings across all changed files.
  • The change is scoped to release automation configuration (CI/CD tooling), meaning there is no impact on runtime behavior, business logic, or end-user-facing SDK functionality.
  • release-please is a mature, Google-maintained release automation tool, making this a low-risk migration from a dependency and maintainability perspective.
  • Full file coverage was achieved (1/1 changed files reviewed), providing confidence that nothing was missed in the analysis.

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