3 Commits

Include renames

Author	SHA1	Message	Date
3 people	a9fe66ca2e	[ci] Move Turbopack, Rspack and font data workflows off of RELEASE_BOT_GITHUB_TOKEN (#93455) ... Co-authored-by: Benjamin Woodruff <[email protected]>	2026-05-05 10:23:01 +02:00
Zack TannerandGitHub	0ea2845cf9	[ci]: fix release script to not strip newlines (#93302) ... The process of signing commits with GH API was stripping newlines. This configures that step to not strip newlines so lint doesn't fail. x-ref: https://github.com/vercel/next.js/actions/runs/25007903789/job/73240317094 <sub>Stack created with <a href="https://github.com/github/gh-stack">GitHub Stacks CLI</a> • <a href="https://gh.io/stacks-feedback">Give Feedback 💬</a></sub>	2026-04-28 18:42:19 +00:00
Zack TannerandGitHub	012fd7df4b	[ci]: trigger signed release commit via API (#93285) ... 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)	2026-04-27 16:31:05 +00:00