mirror of
https://github.com/vercel/next.js.git
synced 2026-09-20 02:25:18 +08:00
Zack Tanner
084f2bcf19
Stacked on https://github.com/vercel/next.js/pull/93245
Commit signing is required for anything that lands on `canary`. Our
previous workflow of using a PAT to push a commit no longer works, since
that would have been an unsigned commit.
In #93245 we switched to an app token for release workflow steps. This
continues by:
- Telling Lerna to bump packages but not commit
- Creating a signed commit with the staged changes via GitHub's API
- Then running the publish flow
Test Plan:
Dry run
[here](https://github.com/vercel/next.js/actions/runs/25001287978/job/73211826479)
Commit
[here](https://github.com/vercel/next.js/commit/3a8456a62b56615e2f8c1d1e6e7b4e14ce89e078)
(cherry picked from commit 012fd7df4b)