Update next in web docs to 15.5.18 for App Router middleware/proxy bypass advisories

[Copilot]

• Install Playwright webkit browser to fix mobile test failures
• Clear turbo build cache and rebuild with changelog snapshot populated from GitHub
• Fix docs-regressions test: update expected changelog heading ID 8-14-1 to a version that exists in the current changelog
• Investigate OSS friends test failure (formbricks.com DNS blocked in sandbox)
• Run full test suite to verify all tests pass

Original prompt

---

This section details the Dependabot vulnerability alert you should resolve

<alert_title>Next.js has a Middleware / Proxy bypass through dynamic route parameter injection</alert_title>
<alert_description>### Impact

Applications that rely on middleware to protect dynamic routes can be vulnerable to authorization bypass. In affected deployments, specially crafted query parameters can alter the dynamic route value seen by the page while leaving the visible path unchanged, which can allow protected content to be rendered without passing the expected middleware check.

Fix

We now only honor internal route-parameter normalization in trusted routing flows and ignore externally supplied parameter encodings that should never have been accepted from ordinary requests.

Workarounds

If you cannot upgrade immediately, enforce authorization in route or page logic instead of relying solely on middleware path matching.</alert_description>

high
GHSA-492v-c6pp-mqqv, CVE-2026-44574
next
npm
<vulnerable_versions>15.5.15</vulnerable_versions>
<patched_version>15.5.16</patched_version>
<manifest_path>temporary/packages/web/docs/package.json</manifest_path>

https://github.com/vercel/next.js/security/advisories/GHSA-492v-c6pp-mqqv https://github.com/vercel/next.js/releases/tag/v15.5.16 https://github.com/vercel/next.js/releases/tag/v16.2.5 https://github.com/advisories/GHSA-492v-c6pp-mqqv

<task_instructions>Resolve this alert by updating the affected package to a non-vulnerable version. Prefer the lowest non-vulnerable version (see the patched_version field above) over the latest to minimize breaking changes. Include a Reachability Assessment section in the PR description. Review the alert_description field to understand which APIs, features, or configurations are affected, then search the codebase for usage of those specific items. If the vulnerable code path is reachable, explain how (which files, APIs, or call sites use the affected functionality) and note that the codebase is actively exposed to this vulnerability. If the vulnerable code path is not reachable, explain why (e.g. the affected API is never called, the vulnerable configuration is not used) and note that the update is primarily to satisfy vulnerability scanners rather than to address an active risk. If the advisory is too vague to determine reachability (e.g. 'improper input validation' with no specific API named), state that reachability could not be determined and explain why. Include a confidence level in the reachability assessment (e.g. high confidence if the advisory names a specific API and you confirmed it is or is not called, low confidence if the usage is indirect and hard to trace). If no patched version is available, check the alert_description field for a Workarounds section — the advisory may describe configuration changes or usage patterns that mitigate the vulnerability without a version update. If a workaround is available, apply it and leave a code comment referencing the advisory identifier explaining it is a temporary mitigation. If neither a patch nor a workaround is available, explain in the PR description why the alert cannot be resolved automatically so a human reviewer can take over. Inspect the repository to determine which package manager is used (e.g. lock files, config files, build scripts) and use that tooling to perform the update — do not edit lock files directly. If the version constraint in the manifest (e.g. package.json, Gemfile, pyproject.toml) caps the version below the fix, update the constraint first. For transitive dependencies, determine whether it is simpler to update the direct dependency that pulls in the vulnerable package or to update the transitive dependency directly, and choose the least disruptive approach. If upgrading to fix the vulnerability forces a major version bump or known breaking changes, review the changelog or release notes, then audit the codebase for usage of affected APIs and fix any breaking changes that are found. If the package manager fails to resolve dependencies (e.g. peer dependency conflicts, incompatible engine constraints), document the error in the PR description rather than attempting increasingly complex workarounds. After updating, check the lock file to confirm the package no longer resolves to a version in the vulnerable range. Keep changes minimal and tightly scoped. Ensure tests, build, type checking, and linting all pass after your changes. If there are any test, lint, or typechecking failures, investigate whether they are caused by the update and fix them if so — do not leave broken tests in the PR. If they were already present before the update, note them in the PR description so a human reviewer can assess whether they are related.</task_instructions>

• Resolves graphql-hive/docs alert Fix backgrounds, headings, and mermaid styling #16

[github-actions]

Deployment	URL
🌐 Website	https://468ead8a-hive-platform-docs.theguild.workers.dev
📚 Storybook	https://pr-114.the-guild-docs-storybook.pages.dev

[Copilot]

Pull request overview

This PR updates the Next.js dependency used by the web docs app to address the reported Middleware / Proxy bypass vulnerability advisory affecting next@15.5.15.

Changes:

• Bump next from 15.5.15 to 15.5.18 in temporary/packages/web/docs.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.