build(deps): bump next and eslint-config-next to 16.4.6

16.4.6 keeps a single header value as a string, so the compression
middleware now sees a route handler's Content-Type and gzips the
response when the client accepts it. Route handlers were never
compressed before. Measured on a production build: JSON and CSV
exports go out gzipped with their Content-Disposition intact and still
flush chunk by chunk, so a streamed download keeps arriving as it is
written. The Coach and document chat streams send
Cache-Control: no-transform, which the middleware honours, so they stay
uncompressed and each frame arrives when it is written. A guard now
holds every text/event-stream surface to that directive.

The notification journey failed twice on the release candidate at the
same step: the e-mail address typed into the card was wiped. The spec
waited for the settings read with waitForResponse, which settles on the
headers, and treated that as the card having copied the server value
into the input. With compression the body follows the headers after a
round through zlib on the thread pool, which a loaded runner can hold
up, and the late copy overwrote the typed value. The spec now also
waits for each card's enable switch, which is disabled until its read
has landed and is enabled in the same render that does the copy.
This commit is contained in:
Marc-André Bombeck committed 2026-11-15 23:43:32 +01:00
1 parent f602336fcb
commit 6debd62326
5 files changed
+136 -56

No files matched your search

+2 -2
View File
@@ -80,7 +80,7 @@
"jspdf-autotable": "^5.0.9",
"lucide-react": "^1.72.0",
"mmdb-lib": "^3.0.5",
"next": "16.4.5",
"next": "16.4.6",
"nodemailer": "10.5.0",
"otpauth": "^9.6.0",
"p-limit": "^7.3.3",
@@ -125,7 +125,7 @@
"@vitest/coverage-v8": "^5.1.0",
"ajv": "^8.20.0",
"eslint": "^9",
"eslint-config-next": "16.4.5",
"eslint-config-next": "16.4.6",
"fast-check": "4.10.2",
"knip": "^6.45.1",
"lefthook": "^2.2.2",