fix(ci): enable automatic Release PR creation in changesets workflow#543
Merged
fix(ci): enable automatic Release PR creation in changesets workflow#543
Conversation
- Set 'commit: true' in .changeset/config.json so changesets/action@v1 can commit version changes - Add commitMessage template to match release prefix - Add 'title' option to changesets/action for consistent Release PR naming - Without these fixes, Release PR was not being created despite 14 pending changesets This enables the full workflow: 1. changesets.yml detects changesets and creates 'Version Packages' PR 2. PR merges → publish step runs (changeset:tag) 3. GitHub release created → release.yml builds Docker image Also fix: format if/else blocks in rate-limiter test to meet linting standards
- Add 'contents: write' for committing version changes - Add 'pull-requests: write' for creating Release PRs These permissions are required for changesets/action to properly create and manage the Release PR workflow.
Collaborator
|
coverage: 73.17%. remained the same — changesets-migration into main |
cameri
approved these changes
Apr 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes the changesets workflow to properly create Release PRs when changesets are detected on the main branch.
Problem
The changesets workflow had two critical issues preventing automatic Release PR creation:
.changeset/config.jsonhad"commit": false, which preventedchangesets/action@v1from committing version changescontents: writeandpull-requests: writepermissionsAs a result, 14 pending changesets from 69 commits since v2.1.0 were not being released.
Changes
1. Enable commits in changeset config (commit
1ff7c04)"commit": truein.changeset/config.jsoncommitMessagetemplate for consistency:"chore(release): version packages\n\n[skip ci]""chore(release): version packages"2. Add workflow permissions (commit
7955109)permissions: contents: write(to commit version changes)permissions: pull-requests: write(to create Release PRs)3. Fix linting violation
test/integration/features/rate-limiter/rate-limiter.tsto meet linting standardsHow the Release Pipeline Now Works
.changeset/entrieschangesets.ymlruns on push to mainnpm run changeset:versionupdatespackage.jsonandCHANGELOG.mdnpm run changeset:tagcreates git tagsrelease.ymlworkflow triggered → image pushed to GHCRVerification
Next Step
Merge this PR to enable automatic Release PR creation on the next push to main.