[danielroe]

🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

port of #4651 to main

currently setting a headers route rule means we clobber any other rules, e.g. caching rules, and always fall to a function

discovered while debugging an issue with @larbish and @atinux

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
nitro.build	Ready	Preview	Sep 22, 2026 7:52pm UTC

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 8382798a-ff5d-46dd-860b-3852ace5129c

📥 Commits

Reviewing files that changed from the base of the PR and between 1e42875 and 2c1e248.

📒 Files selected for processing (2)

• src/presets/vercel/utils.ts
• test/presets/vercel.test.ts

Included review availability: Your plan provides up to 10 included reviews per hour; 8 remain after this review.

---

📝 Walkthrough

Walkthrough

Changes

Vercel header-only routes now omit continue: true when redirect: false. Tests verify that the route keeps its headers and appears before the less-specific redirect route.

Vercel route continuation

Layer / File(s)	Summary
Conditional header route continuation src/presets/vercel/utils.ts	generateBuildConfig omits continue: true for header-only routes with redirect: false.
Generated route ordering validation test/presets/vercel.test.ts	The fixture, snapshot, and test validate the preserved header, route ordering, and omitted continue property.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Bug fix

Merge Risk: ⚪ Minimal · up to 2c1e2

The PR is mergeable with no concrete unresolved risk identified in the reviewed scope.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 2 files.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title follows Conventional Commits format with the fix(vercel): prefix and describes the header-only route behavior changed by the pull request.
Description check	✅ Passed	The description clearly identifies the Vercel header-rule bug, its effect on other route rules, and the purpose of the fix.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

• Fix all pre-merge checks with AI

✨ Finishing Touches 💡 1

📝 Generate docstrings 💡

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/nitro@4652

commit: 2c1e248

[pi0x]

On top of the first commit: 1e42875 orders header-only routes from least to most specific so the more specific rule wins under continue, and 2c1e248 drops continue for header rules with redirect: false so a broader redirect (e.g. /foo/**) no longer redirects them at the edge. Verified with a real Vercel deployment against main: public asset immutable caching now works, header precedence is correct, and ISR/CDN caching is unchanged.

Written with AI assistance.