Skip to content

ci: add automated release workflow - #78

Open
zimeg wants to merge 9 commits into
mainfrom
release-workflow
Open

ci: add automated release workflow#78
zimeg wants to merge 9 commits into
mainfrom
release-workflow

Conversation

@zimeg

@zimeg zimeg commented Jun 23, 2026

Copy link
Copy Markdown
Member

Summary

This PR automates the release process using a "changesets" inspired PR flow 🚀 ✨

Preview

#81

Category

  • Others

Requirements

  • I've read and agree to the Code of Conduct.
  • I've run ./scripts/install_all_and_run_tests.sh after making the changes.

zimeg and others added 3 commits June 23, 2026 08:57
Opens and maintains a release PR that bumps the $ref version in
manifest.schema.json, modelled on slack-cli's release workflow. The
workflow decides the next semver version from semver:* labels on PRs
merged since the latest tag, rewrites the pinned $ref URLs, commits
'version X.Y.Z', tags it, and opens/updates a draft PR from the rc
branch.

Mutating steps are gated on the GH_APP_ID secret and skip on
pull_request events, so the workflow can run in dry-run mode for
testing before the GitHub App secrets are added.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@zimeg
zimeg force-pushed the release-workflow branch from 002b9d8 to ead75c7 Compare June 23, 2026 15:57
zimeg and others added 6 commits June 23, 2026 09:00
The workflow now always uses the GitHub App token. The pull_request
trigger is kept temporarily for testing and will be removed before
merge.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Use the slackapi[bot] user's numeric id (186980925) for the commit
email, matching java-slack-sdk-runner, and scope the App token to this
repository.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Rewrite the Production Deployment section to describe the release PR
flow: label PRs with semver:*, then review and merge the generated
release candidate. Refine the workflow comments alongside.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
- Abort the version decision if a PR label lookup fails, rather than
  silently under-bumping to patch.
- Clarify the tag-lookup and PR-scan comments.
- Point the maintainers guide at the PRs behind main's commits for
  semver labels.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@zimeg zimeg self-assigned this Jun 23, 2026
@zimeg zimeg added github_actions Continuous integration changes semver:patch release labels Jun 23, 2026
@zimeg
zimeg marked this pull request as ready for review June 23, 2026 17:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

github_actions Continuous integration changes release semver:patch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant