Bump next from 13.4.12 to 15.5.0 in /website

[dependabot]

Bumps next from 13.4.12 to 15.5.0.

Release notes

Sourced from next's releases.

v15.5.0

Core Changes

• Use and enforce exhaustive switch statements for work unit store: #81577
• Enable @typescript-eslint/switch-exhaustiveness-check rule: #81583
• [dynamicIO] use RSC dynamicness to control partial vs complete PPR result: #81627
• [dynamicIO] Do not use React.unstable_postpone(): #81652
• feat: new detachable panel UI: #81483
• Turbopack: content-hash PageLoaderAsset: #81450
• [segment explorer] fix content overflow styling: #81649
• Improve reliability of owner stacks for async I/O errors: #81501
• fix(router): Prevent redirect loop on root data requests with basePath: #81096
• Ensure custom NextServer config is honored: #81681
• Fix before interactive incorrectly render css: #81146
• perf: memorize exclude function in webpack config: #81525
• Also enforce experimental features when there's no next config file: #81679
• feat(next/image): warn when images.qualities is undefined: #81690
• feat(build): optimize filterUniqueParamsCombinations to generate sub-combinations: #81321
• Update NextAdapter type and re-export: #81692
• upgrade to path-to-regexp@6.3.0: #80123
• [metadata] replace for initial body icon case: #81688
• [segment explorer] remove dev panel ui flag: #81670
• Simplify running test apps locally with ppr or dynamicIO enabled: #81668
• [turbopack] Return cached Promise from __turbopack_load_by_url__ : #81663
• Upgrade React from 97cdd5d3-20250710 to 2f0e7e57-20250715: #81678
• Delete unused renderToString function: #81707
• Discard prerendered route handler data from FS cache after revalidation: #81611
• Upgrade React from 2f0e7e57-20250715 to d85ec5f5-20250716: #81708
• Ignore pending revalidations during prerendering: #81621
• [turbopack] Clear chunk cache on HMR instead of creating new next-server VM: #81664
• fix: rootParams should throw in client when fallbackParams are not present: #81711
• perf(build): optimize buildAppStaticPaths performance and add helper function: #81386
• Turbopack: Support string without options for @​next/mdx: #81713
• [Segment Cache] Support dynamic head prefetching: #81677
• [sourcemaps] Consistent cursor columns: #81375
• fix: revert client segment route changes for sub shell generation: #81731
• fix: pages router metadata bugs with React 19: #81733
• Improve error handling for headers/cookies/draftMode in 'use cache': #81716
• [devtool] fix duplicate rendered indicator on server: #81729
• [devtool] enable segment explorer by default: #81737
• [turbopack] Stop exposing globals from Turbopack runtime: #81727
• Remove unnecessary await: #81761
• [chore] bump zod to latest v3: #81757
• feat(turbopack): Log anonymized internal error (panic) information to telemetry: #81272
• fix: revert client segment route changes for sub shell generation: #81740
• bugfix: static resources staleTime should be renewed once refetched: #81771
• [devtool] move font styling to global.css: #81782
• [devtool] copy decoded info of error details: #81735
• fix(build): add sourcePage context for PPR dynamic route lambda creation: #81781
• refactor: rename experimental.dynamicIO to experimental.cacheComponents: #81562

... (truncated)

Commits

• 7e08c82 v15.5.0
• 77bb702 docs: add explanation of disabling lint for next build (#82805)
• 8f6d345 v15.4.2-canary.56
• 533bcd1 docs: Route props helpers, typegen and next lint deprecation (#82784)
• e6718d6 docs: fix TS error in Node.js runtime local assets example (#82672)
• 91da003 fix: remove a few old references to 'next lint' (#82800)
• e3e2197 v15.4.2-canary.55
• 408920c fix: possible null access (#82799)
• 4e9cc18 fix: don't fail with amp config in JS (#82798)
• c57fe25 feat: add a codemod to migrate from the deprecated "next lint" command (#82685)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	form-data@​4.0.0
	crypto-js@​4.1.1
	number-is-nan@​1.0.1
	@​docsearch/​css@​3.3.3
	@​algolia/​logger-console@​4.17.0
	@​algolia/​logger-common@​4.17.0
	@​algolia/​cache-in-memory@​4.17.0
	@​algolia/​requester-common@​4.17.0
	docusaurus-plugin-proxy@​0.6.3
	@​algolia/​requester-browser-xhr@​4.17.0
	@​algolia/​cache-browser-local-storage@​4.17.0
	@​algolia/​client-account@​4.17.0
	@​algolia/​cache-common@​4.17.0
	@​algolia/​client-personalization@​4.17.0
	@​algolia/​requester-node-http@​4.17.0
	oas-kit-common@​1.0.8
	@​algolia/​autocomplete-shared@​1.7.4
	@​algolia/​client-common@​4.17.0
	@​algolia/​client-analytics@​4.17.0
	http-reasons@​0.1.0
	dezalgo@​1.0.4
	@​types/​hoist-non-react-statics@​3.3.1
	@​algolia/​transporter@​4.17.0
	fbjs-css-vars@​1.0.2
	lodash.isstring@​4.0.1
	lodash.isplainobject@​4.0.6
	@​algolia/​client-search@​4.17.0
	lodash.escaperegexp@​4.1.2
	docusaurus-theme-openapi@​0.6.4
	decamelize@​1.2.0
	array-uniq@​1.0.3
	path@​0.12.7
See 92 more rows in the dashboard

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		crypto-js@4.1.1 has a Critical CVE. CVE: GHSA-xwcq-pm8m-c4vf crypto-js PBKDF2 1,000 times weaker than specified in 1993 and 1.3M times weaker than current standard (CRITICAL) Affected versions: < 4.2.0 Patched version: 4.2.0 From: docs/yarn.lock → npm/crypto-js@4.1.1 ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/crypto-js@4.1.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		form-data@4.0.0 has a Critical CVE. CVE: GHSA-fjxv-7rqg-78g4 form-data uses unsafe random function in form-data for choosing boundary (CRITICAL) Affected versions: < 2.5.4; >= 3.0.0 < 3.0.4; >= 4.0.0 < 4.0.4 Patched version: 4.0.4 From: docs/yarn.lock → npm/form-data@4.0.0 ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/form-data@4.0.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[dependabot]

Superseded by #44.