[marckong]

Tracking

Companion to Kong/volcano-hosting#3436.

Why

Kong/volcano-hosting#3436 pins Next.js 16.4.6 in place of 16.4.5. The frontend endpoints reference names the pinned versions and their engines.node ranges.

Summary

• content/platform/api-reference/frontend-endpoints.md: Next 16.4.5 → 16.4.6. The engines.node range (>=20.9.0) is the same for both versions.
• The cookbooks' "Tested on … next 16.4.5" lines record what each cookbook was verified with, so they stay as they are.

Merge this when Kong/volcano-hosting#3436 reaches production.

Verification

• node scripts/lint-docs.mjs content/platform/api-reference: docs OK.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.

[github-actions]

AI review: no P0-P2 findings

Reviewed 1729ff4. Run log

This PR changes one line in content/platform/api-reference/frontend-endpoints.md: the tested Next.js 16 pin goes from 16.4.5 to 16.4.6, and the engines.node range stays >=20.9.0. It is low risk. No other page names the pin as the current tested version; the cookbooks' "Tested on" lines record what each was verified with, so they correctly stay unchanged.

Not checked: The AI review read the diff, the code, and the PR's text; it ran no tests or builds and read nothing outside this repository.

• The release-timing rule in spec/writing.md means this should merge only once Kong/volcano-hosting#3436 (the 16.4.6 pin) is running in production.
• The npm metadata for next@​16.4.6 should declare engines.node as >=20.9.0, as the page now says.
• Verify that Kong/volcano-hosting#3436 reaches production before merging and that its Next.js 16.4.6 pin has the stated Node.js requirement.

Human review: not needed