mirror of
https://github.com/vercel/next.js.git
synced 2026-09-20 02:25:18 +08:00
Sebastian "Sebbie" Silbermann
28195e9b75
Code freezes are now managed by toggling the existing `code freeze` repository ruleset in the repository settings, so the `code_freeze` workflow is no longer needed. It was also broken beyond repair: it targeted the legacy branch-protection API with a `CODE_FREEZE_TOKEN` secret that no longer exists instead of the rulesets the repository uses now, and it referenced a `releaseType` input that was never declared. This PR deletes the workflow and `scripts/code-freeze.js`, which had no other consumer. Note on the investigated alternative: resurrecting the workflow on top of the rulesets API with just `GITHUB_TOKEN` is not possible. Creating or updating repository rulesets requires the "Administration" repository permission, which the workflow token cannot be granted (`permissions: administration: write` is rejected as an invalid workflow, and even `write-all` gets `403 Resource not accessible by integration`). Verified empirically in https://github.com/eps1lon/github-actions-repository-dispatch-admin-permissions. Co-authored-by: Claude Code (kimi-k3[1m]) <noreply@anthropic.com>