Release React Router

Use the existing release automation. Read DEVELOPMENT.md, .github/workflows/release.yml, and scripts/changes/{pr,publish}.ts for the current process and tag rules. This skill covers generated release PRs; experimental releases use a separate workflow.

A request to perform a release authorizes merging the verified PR and following publication. A readiness-only request stops with the review. Creating or editing this skill does not authorize a live release.

Review the release PR

• Find the generated release PR in remix-run/react-router, targeting main by default or the requested v7/existing hotfix branch. Confirm its source repository and generated branch match scripts/changes/pr.ts. Attach the PR to the chat when the app provides that tool.
• Record the exact head SHA and current base tip. Require the candidate to contain that tip; otherwise wait for automatic PR regeneration and review the updated head. Use GitHub APIs or fetched Git objects to inspect files without changing the user's checkout.
• Review the diff for the expected package version bumps, root/package changelogs, deleted pending change files, and consumption of scripts/changes/whats-changed.md when present. Confirm the notes represent the pending changes and preserve any manual narrative. Under the current generator, package manifests change only their version; investigate extra paths or fields.
• Capture the expected package/version pairs and their npm/git tags from the candidate and current publish script. Discover the package set and versions each run. For non-main releases, record GitHub's current latest release ID before merging so it can be checked afterward.
• Use PR CI for build, test, typecheck, lint, and integration validation. Check all required and applicable jobs on the reviewed head/test merge, accounting for current workflow path filters and intentional matrix skips. Pending, failed, canceled, missing, or stale checks hold the release. No local dependency install, build, packing, consumer smoke, or regeneration is part of the normal release review.

Report ready/hold with any blockers, the reviewed SHA, and CI evidence. For an authorized release, continue directly when ready. Fix source notes on the base through the normal process if authorized; let automation regenerate the release PR instead of editing its branch.

Merge and follow the workflow