Skip to content

chore: new release processes - #1090

Open
joaodordio wants to merge 1 commit into
masterfrom
chore/new-release-processes
Open

chore: new release processes#1090
joaodordio wants to merge 1 commit into
masterfrom
chore/new-release-processes

Conversation

@joaodordio

Copy link
Copy Markdown
Member

Summary

Replaces the existing ad-hoc release workflows with a standardized two-step process across all SDKs.

Workflow 1: Prepare Release (workflow_dispatch)

Inputs: version, ticket

  • Updates CHANGELOG.md (promotes [Unreleased] to new version section)
  • Bumps all version files
  • Opens a release PR with a checklist
  • Creates a GitHub draft release (no tag created yet, nothing published)

Workflow 2: Publish Release (workflow_dispatch)

Input: version

  • Verifies the prepare-release PR has been merged (checks CHANGELOG on master/main)
  • Publishes the draft release and creates the tag on master/main at this moment
  • Publishes to the SDK's distribution platform
  • Posts to #eng-sdk-team on Slack

Files changed

  • Added .github/workflows/prepare-release.yml
  • Added .github/workflows/publish-release.yml
  • Deleted old release workflow(s)

Secrets to add

SLACK_WEBHOOK must be configured in repo Settings > Secrets > Actions before the first Publish Release run.

Related: [SDK Release Process Team Agreement 2026-09-11]

Replaces the monolithic release workflow with a two-step process:
- Prepare Release: bumps version, updates changelog, opens PR, creates GitHub draft release
- Publish Release: promotes draft, tags master/main, publishes to distribution, posts Slack

Ref: SDK release process team agreement 2026-09-11
@joaodordio
joaodordio requested a review from a team as a code owner September 11, 2026 18:04
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