Skip to content

chore: new release processes - #586

Open
joaodordio wants to merge 4 commits into
mainfrom
chore/new-release-processes
Open

joaodordio wants to merge 4 commits into
mainfrom
chore/new-release-processes

Conversation

@joaodordio

@joaodordio joaodordio commented Sep 11, 2026

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]

No customer facing changes

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
… grep

- Add ref: master/main to actions/checkout in all prepare/publish workflows
  so workflows always operate on the default branch regardless of dispatch ref
- Replace shell-injection-prone ${{ steps...outputs.notes }} pattern with
  --notes-file using $RUNNER_TEMP/release-notes.md (safe from backticks/quotes
  in changelog content)
- Treat empty [Unreleased] section as a hard error in prepare-release
- Fix CHANGELOG verification grep: grep -qE "^## \[VERSION\]" (anchored,
  prevents substring matches and prefix collisions like 3.1.0 vs 3.1.0-rc1)
@codecov-commenter

codecov-commenter commented Sep 16, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 74.43%. Comparing base (b748ec4) to head (553d5cf).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #586   +/-   ##
=======================================
  Coverage   74.43%   74.43%           
=======================================
  Files          57       57           
  Lines        2742     2742           
  Branches      804      821   +17     
=======================================
  Hits         2041     2041           
  Misses        700      700           
  Partials        1        1           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Replace SDK_RELEASE_TOKEN (iOS) and GITHUB_TOKEN (all repos) with a
short-lived installation token from the iterable-sdk-release GitHub App,
generated via actions/create-github-app-token@v1.

Benefits:
- App token triggers CI on PRs it creates (GITHUB_TOKEN cannot)
- 1h TTL vs long-lived PAT
- Workflow-scoped permissions so we can push .github/workflows/ files

Required credentials (repo variable + secret, or set at org level):
  vars.ITERABLE_SDK_RELEASE_APP_ID
  secrets.ITERABLE_SDK_RELEASE_APP_PRIVATE_KEY
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.

2 participants