ci: use GitHub API commit mode for changesets action#1867
Merged
TooTallNate merged 1 commit intomainfrom Apr 29, 2026
Merged
Conversation
The repo enforces "Commits must have verified signatures" via an org/enterprise-level ruleset, which blocks unsigned commits pushed via the Git CLI by GITHUB_TOKEN. Switching the changesets action to commitMode: github-api makes commits GPG-signed by GitHub.
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Contributor
🧪 E2E Test Results❌ Some tests failed Summary
❌ Failed Tests▲ Vercel Production (8 failed)astro (1 failed):
example (1 failed):
express (1 failed):
fastify (1 failed):
nextjs-turbopack (1 failed):
nextjs-webpack (1 failed):
nuxt (1 failed):
vite (1 failed):
Details by Category❌ ▲ Vercel Production
✅ 💻 Local Development
✅ 📦 Local Production
✅ 🐘 Local Postgres
✅ 📋 Other
❌ Some E2E test jobs failed:
Check the workflow run for details. |
Contributor
📊 Benchmark Results
workflow with no steps💻 Local Development
workflow with 1 step💻 Local Development
workflow with 10 sequential steps💻 Local Development
workflow with 25 sequential steps💻 Local Development
workflow with 50 sequential steps💻 Local Development
Promise.all with 10 concurrent steps💻 Local Development
Promise.all with 25 concurrent steps💻 Local Development
Promise.all with 50 concurrent steps💻 Local Development
Promise.race with 10 concurrent steps💻 Local Development
Promise.race with 25 concurrent steps💻 Local Development
Promise.race with 50 concurrent steps💻 Local Development
workflow with 10 sequential data payload steps (10KB)💻 Local Development
workflow with 25 sequential data payload steps (10KB)💻 Local Development
workflow with 50 sequential data payload steps (10KB)💻 Local Development
workflow with 10 concurrent data payload steps (10KB)💻 Local Development
workflow with 25 concurrent data payload steps (10KB)💻 Local Development
workflow with 50 concurrent data payload steps (10KB)💻 Local Development
Stream Benchmarks (includes TTFB metrics)workflow with stream💻 Local Development
stream pipeline with 5 transform steps (1MB)💻 Local Development
10 parallel streams (1MB each)💻 Local Development
fan-out fan-in 10 streams (1MB each)💻 Local Development
SummaryFastest Framework by WorldWinner determined by most benchmark wins
Fastest World by FrameworkWinner determined by most benchmark wins
Column Definitions
Worlds:
❌ Some benchmark jobs failed:
Check the workflow run for details. |
karthikscale3
approved these changes
Apr 29, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the Release workflow to satisfy repository rulesets that require verified/signed commits by switching changesets’ commit mechanism to the GitHub API (which produces GitHub-verified commits), preventing failures when pushing the version PR commit.
Changes:
- Configure
changesets/actionto usecommitMode: github-apito create verified commits via the GitHub REST API. - Add an inline comment explaining why the GitHub API commit mode is required.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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
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
Follow-up to #1866. The Release workflow failed when trying to push the "Version Packages" PR commit to
changeset-release/main:Org/enterprise-level rulesets require verified signatures on all branches in the repo. Commits pushed via the Git CLI using
GITHUB_TOKENare not signed.This PR switches
changesets/actiontocommitMode: github-api, which creates commits via the GitHub REST API. Commits made through the API are automatically GPG-signed by GitHub and therefore satisfy the signature requirement.Note on backport workflow
backport.ymlstill pushes cherry-picks tostableviagit push, which will likely also fail the signature rule. That can be addressed in a follow-up PR if/when the backport flow is exercised — the manual fallback documented in the workflow's failure comment still works.