chore(deps): bump the npm-dependencies group across 1 directory with 42 updates

[dependabot]

Bumps the npm-dependencies group with 42 updates in the / directory:

Package	From	To
@clickhouse/client	1.18.2	1.23.1
@filoz/synapse-core	0.3.3	0.7.0
@nestjs/common	11.1.13	11.1.28
@nestjs/config	4.0.3	4.0.4
@nestjs/core	11.1.13	11.1.28
@nestjs/platform-express	11.1.13	11.1.28
@nestjs/schedule	6.1.1	6.1.3
@nestjs/swagger	11.2.6	11.4.6
@nestjs/typeorm	11.0.0	11.0.3
@willsoto/nestjs-prometheus	6.0.2	6.1.0
axios	1.13.5	1.18.1
class-validator	0.14.3	0.15.1
helmet	8.1.0	8.3.0
joi	18.0.2	18.2.3
multiformats	14.0.4	14.0.5
pg	8.18.0	8.22.0
pg-boss	12.11.1	12.26.3
viem	2.48.11	2.55.8
@nestjs/cli	11.0.16	11.0.24
@nestjs/schematics	11.0.9	11.1.0
@nestjs/testing	11.1.13	11.1.28
ts-loader	9.5.4	9.6.2
assemblyscript	0.19.23	0.28.20
@radix-ui/react-slot	1.2.4	1.3.3
@radix-ui/react-switch	1.2.6	1.3.7
@radix-ui/react-tabs	1.1.13	1.1.21
@tailwindcss/vite	4.2.4	4.3.3
date-fns	4.1.0	4.4.0
lucide-react	1.24.0	1.27.0
react	19.2.5	19.2.8
@types/react	19.2.14	19.2.17
react-dom	19.2.5	19.2.8
react-router-dom	7.13.0	7.18.1
recharts	3.7.0	3.10.1
swr	2.4.1	2.4.2
tailwind-merge	3.5.0	3.6.0
tailwindcss	4.2.4	4.3.3
msw	2.12.10	2.15.0
@biomejs/biome	2.3.14	2.5.5
@swc/core	1.15.11	1.15.46
@vitest/coverage-v8	4.0.18	4.1.10
vitest	4.0.18	4.1.10

Updates @clickhouse/client from 1.18.2 to 1.23.1

Release notes

Sourced from @​clickhouse/client's releases.

client-1.23.1

Bug Fixes

• Re-export EXCEPTION_TAG_HEADER_NAME and extractErrorAtTheEndOfChunk from @clickhouse/client. Both are part of the (now deprecated) @clickhouse/client-common public API but were missed when its surface was bundled into and re-exported from the client packages in 1.23.0 (#845). Reported downstream by Langfuse. (#935)

#935: ClickHouse/clickhouse-js#935

#845: ClickHouse/clickhouse-js#845

client-web-1.23.1

Bug Fixes

• Re-export EXCEPTION_TAG_HEADER_NAME and extractErrorAtTheEndOfChunk from @clickhouse/client-web. Both are part of the (now deprecated) @clickhouse/client-common public API but were missed when its surface was bundled into and re-exported from the client packages in 1.23.0 (#845). Reported downstream by Langfuse. (#935)

#935: ClickHouse/clickhouse-js#935

#845: ClickHouse/clickhouse-js#845

client-1.23.0

Migration Notes

• Node.js 26.x was added to the CI matrix, and Node.js 18.x is no longer supported. The engines.node floor of @clickhouse/client (previously >=16) and @clickhouse/datatype-parser (previously >=18.0.0) was raised to >=20. Node.js 20.x, 22.x, 24.x, and 26.x are supported and exercised in CI.

• The @clickhouse/client-common package is deprecated. @clickhouse/client (Node.js) and @clickhouse/client-web (Web) no longer depend on it; the shared code is now bundled into each client package. Everything previously importable from @clickhouse/client-common should be imported from @clickhouse/client or @clickhouse/client-web instead. The @clickhouse/client-common package itself will no longer receive updates. (#845)

• The parseColumnType function and its SimpleColumnTypes companion (exported from @clickhouse/client, @clickhouse/client-web, and @clickhouse/client-common) are deprecated and slated for removal in a future major version. They are superseded by the new standalone @clickhouse/datatype-parser package (parseDataType plus its Node AST), which parses the full ClickHouse data-type grammar and emits an AST that mirrors the server's. (#893)

New features

• (Node.js) Added a RowBinary reader library and agent skill under skills/clickhouse-js-node-rowbinary-parser. It ships type-specific, monomorphizable building blocks for decoding RowBinary / RowBinaryWithNames / RowBinaryWithNamesAndTypes streams (full-buffer and chunked), plus a skill that guides an agent to generate bespoke high-performance parsers from a query's column types. The skill is bundled into @clickhouse/client (registered in agents.skills) and is also published independently as the @clickhouse/rowbinary package. A matching RowBinary writer is planned. (#864)

• Published the @clickhouse/datatype-parser package: a small, dependency-free standalone parser for ClickHouse data-type strings (the kind sent in the types row of RowBinaryWithNamesAndTypes, e.g. Array(Nullable(UInt64)), Tuple(a UInt8, b String), Enum8('a' = 1)). It is a faithful port of the server's ParserDataType and emits a JSON AST that is byte-identical to the server's EXPLAIN AST json = 1 data-type subtree. It supersedes the deprecated parseColumnType (see Migration Notes). (#893)

• (Node.js, @experimental) Added an additive connection?: Connection<Stream.Readable> option to createClient that lets a caller plug an externally-built backend Connection-like object in place of the default HTTP(S) factory. Only supposed to be used for testing the chDB integration. (#879)

• Added ClickHouseSettingsInterface, a package-neutral structural counterpart to ClickHouseSettings, exported from @clickhouse/client, @clickhouse/client-web, and @clickhouse/client-common. It is identical to ClickHouseSettings except that its index signature omits SettingsMap (a class with a private member, which TypeScript compares nominally). Because each client package now bundles its own copy of the common module, their ClickHouseSettings types are mutually unassignable; ClickHouseSettingsInterface is structurally identical across all three packages and assignable into each package's ClickHouseSettings, so a consumer that shares a single settings-producing helper across both the Node.js and Web clients can type it against this one type without casts. Values typed as SettingsMap cannot be carried through it — use ClickHouseSettings if you need them. (#889)

#845: ClickHouse/clickhouse-js#845 #864: ClickHouse/clickhouse-js#864 #879: ClickHouse/clickhouse-js#879 #889: ClickHouse/clickhouse-js#889 #893: ClickHouse/clickhouse-js#893

client-common-1.23.0

Migration Notes

• Node.js 26.x was added to the CI matrix, and Node.js 18.x is no longer supported. The engines.node floor of @clickhouse/client (previously >=16) and @clickhouse/datatype-parser (previously >=18.0.0) was raised to >=20. Node.js 20.x, 22.x, 24.x, and 26.x are supported and exercised in CI.

... (truncated)

Changelog

Sourced from @​clickhouse/client's changelog.

[!IMPORTANT] This repository-wide changelog is frozen. New entries now live in each package's own CHANGELOG.md:

• @clickhouse/client → https://github.com/ClickHouse/clickhouse-js/blob/main/packages/client-node/CHANGELOG.md
• @clickhouse/client-web → https://github.com/ClickHouse/clickhouse-js/blob/main/packages/client-web/CHANGELOG.md
• @clickhouse/client-common (deprecated) → https://github.com/ClickHouse/clickhouse-js/blob/main/packages/client-common/CHANGELOG.md
• @clickhouse/datatype-parser → https://github.com/ClickHouse/clickhouse-js/blob/main/packages/datatype-parser/CHANGELOG.md
• @clickhouse/rowbinary → https://github.com/ClickHouse/clickhouse-js/blob/main/skills/clickhouse-js-node-rowbinary-parser/CHANGELOG.md

The history below (through @clickhouse/client 1.23.0) is retained for reference and was copied as-is into each client package's changelog as the starting point for the split.

1.23.0

Migration Notes

• Node.js 26.x was added to the CI matrix, and Node.js 18.x is no longer supported. The engines.node floor of @clickhouse/client (previously >=16) and @clickhouse/datatype-parser (previously >=18.0.0) was raised to >=20. Node.js 20.x, 22.x, 24.x, and 26.x are supported and exercised in CI.

• The @clickhouse/client-common package is deprecated. @clickhouse/client (Node.js) and @clickhouse/client-web (Web) no longer depend on it; the shared code is now bundled into each client package. Everything previously importable from @clickhouse/client-common should be imported from @clickhouse/client or @clickhouse/client-web instead. The @clickhouse/client-common package itself will no longer receive updates. (#845)

• The parseColumnType function and its SimpleColumnTypes companion (exported from @clickhouse/client, @clickhouse/client-web, and @clickhouse/client-common) are deprecated and slated for removal in a future major version. They are superseded by the new standalone @clickhouse/datatype-parser package (parseDataType plus its Node AST), which parses the full ClickHouse data-type grammar and emits an AST that mirrors the server's. (#893)

New features

• (Node.js) Added a RowBinary reader library and agent skill under skills/clickhouse-js-node-rowbinary-parser. It ships type-specific, monomorphizable building blocks for decoding RowBinary / RowBinaryWithNames / RowBinaryWithNamesAndTypes streams (full-buffer and chunked), plus a skill that guides an agent to generate bespoke high-performance parsers from a query's column types. The skill is bundled into @clickhouse/client (registered in agents.skills) and is also published independently as the @clickhouse/rowbinary package. A matching RowBinary writer is planned. (#864)

• Published the @clickhouse/datatype-parser package: a small, dependency-free standalone parser for ClickHouse data-type strings (the kind sent in the types row of RowBinaryWithNamesAndTypes, e.g. Array(Nullable(UInt64)), Tuple(a UInt8, b String), Enum8('a' = 1)). It is a faithful port of the server's ParserDataType and emits a JSON AST that is byte-identical to the server's EXPLAIN AST json = 1 data-type subtree. It supersedes the deprecated parseColumnType (see Migration Notes). (#893)

• (Node.js, @experimental) Added an additive connection?: Connection<Stream.Readable> option to createClient that lets a caller plug an externally-built backend Connection-like object in place of the default HTTP(S) factory. Only supposed to be used for testing the chDB integration. (#879)

• Added ClickHouseSettingsInterface, a package-neutral structural counterpart to ClickHouseSettings, exported from @clickhouse/client, @clickhouse/client-web, and @clickhouse/client-common. It is identical to ClickHouseSettings except that its index signature omits SettingsMap (a class with a private member, which TypeScript compares nominally). Because each client package now bundles its own copy of the common module, their ClickHouseSettings types are mutually unassignable; ClickHouseSettingsInterface is structurally identical across all three packages and assignable into each package's ClickHouseSettings, so a consumer that shares a single settings-producing helper across both the Node.js and Web clients can type it against this one type without casts. Values typed as SettingsMap cannot be carried through it — use ClickHouseSettings if you need them. (#889)

1.22.0

New features

• (Node.js) The compression.request / compression.response client options now accept an explicit codec via an object, in addition to the existing boolean: true keeps gzip (backwards compatible), and { codec: "zstd" } selects zstd. The object form is intentionally extensible for future codecs and codec-specific options. zstd typically yields a similar-or-better ratio than gzip at noticeably lower CPU cost (gzip/DEFLATE is comparatively CPU-heavy and decompressed single-threaded by the ClickHouse server), and it uses the built-in zlib zstd support, so it requires Node.js >= 22.15.0 (@clickhouse/client throws a clear error at client creation otherwise). Response decompression is driven by the server's actual Content-Encoding, so it degrades gracefully. The request object form also accepts an optional level ({ codec, level }) to set the codec-specific compression level (zlib level for gzip, zstd compression level for zstd); the response compression level is controlled by the server. Supported only by @clickhouse/client (Node.js); @clickhouse/client-web rejects the zstd codec at client creation.

• (Node.js) Brotli ({ codec: "br" }) is now supported for compression.request / compression.response, alongside gzip and zstd. Unlike zstd, Brotli is available on every supported Node.js version (no minimum-version requirement). The compression.request option is a per-codec discriminated union, so each codec exposes its own tuning option: a level for gzip/zstd, a quality for Brotli ({ codec: "br", quality }). When omitted, Brotli defaults to quality 4 for request bodies, since zlib's brotli default of 11 (max) is far too slow for a streaming insert path. Response decompression follows the server's Content-Encoding. Supported only by @clickhouse/client (Node.js).

Internal changes (@clickhouse/client-common)

These only affect code that imports the low-level connection primitives from the deprecated @clickhouse/client-common package directly (e.g. a custom Connection implementation). The createClient compression option is unchanged and fully backwards compatible — if you only use @clickhouse/client or @clickhouse/client-web, you are not affected.

To carry the codec (and its optional compression level) instead of a bare on/off flag, the internal compression representation changed shape:

• CompressionSettings.compress_request / decompress_response are no longer boolean. They are now a normalized codec object or undefined (disabled): { codec: "gzip" | "zstd"; level?: number } | { codec: "br"; quality?: number } for the request, { codec: "gzip" | "zstd" | "br" } for the response (response compression options are chosen by the server). getConnectionParams normalizes the public request option into this form (true → { codec: "gzip" }).
• withCompressionHeaders now takes request_compression_codec / response_compression_codec (a CompressionMethod | undefined) instead of the boolean enable_request_compression / enable_response_compression; the codec value is also the Content-Encoding / Accept-Encoding it emits.

... (truncated)

Commits

• f67717b Merge pull request #941 from ClickHouse/main
• 3bccc81 chore: bump @​clickhouse/client-web version to 1.23.1 (#940)
• cc9383c chore: bump @​clickhouse/client version to 1.23.1 (#939)
• 8415878 fix(ci): lockfile-age-audit — request full packument so time is present (#888)
• 71b2e8a Merge pull request #936 from ClickHouse/main
• a417d5c fix(client): re-export EXCEPTION_TAG_HEADER_NAME and extractErrorAtTheEndOfCh...
• 305030d Separate per-package READMEs and stop prepack from overwriting them (#934)
• 8c51d9a ci: run RowBinary skill benchmarks on a live ClickHouse (#933)
• 199f994 Embed Vitest configs into client packages; run common tests from node/web (#931)
• ed25b25 Run web Vitest browser tests headless by default (#930)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​clickhouse/client since your current version.

Updates @filoz/synapse-core from 0.3.3 to 0.7.0

Release notes

Sourced from @​filoz/synapse-core's releases.

synapse-core: v0.7.0

0.7.0 (2026-06-11)

⚠ BREAKING CHANGES

• costs: per-operation pricing price list (#823)
• provider-relayed service termination as the default path (#827)

Features

• costs: per-operation pricing price list (#823) (66af832)
• provider-relayed service termination as the default path (#827) (06152d0)

Bug Fixes

• synapse-core: update filecoin-services ref to v1.3.0 (#831) (b500c44)
• update termination service error handling and response schemas (#842) (71b300f)

Chores

• synapse-core: update filecoin-services ref to final v1.3.0 deployments (#844) (94e2a0d)
• update to pnpm 11 and dependencies across multiple packages (95a620c)

synapse-core: v0.6.1

0.6.1 (2026-06-09)

Bug Fixes

• synapse-core: keep findPiece polling through transient 404s (#828) (fadc836)

synapse-core: v0.6.0

0.6.0 (2026-06-04)

⚠ BREAKING CHANGES

• typehash: DeleteDataSetPermission is replaced by TerminateServicePermission. Existing session keys must be re-minted; passing a stale session key to Synapse.create() fails because the default permission set no longer matches.
• piece: vendor PieceCID, redesign API (#795)

Features

• cap addPieces batches at 40, tighten piece metadata limits (#814) (06b4f65)
• piece: vendor PieceCID, redesign API (#795) (ec0c254)

Bug Fixes

... (truncated)

Changelog

Sourced from @​filoz/synapse-core's changelog.

0.7.0 (2025-06-10)

Features

• storage: implement smart provider selection to prefer existing relationships (8433899)

0.6.1 (2025-06-10)

Trivial Changes

• deps-dev: bump @​types/node from 22.15.31 to 24.0.0 (fecfaa5)

0.6.0 (2025-06-10)

Features

• utils: add Pandora storage provider admin portal [skip ci] (#79) (e6a79bc)

Bug Fixes

• remove 60s delay after createproofset and associated testing hack (353551a)

Trivial Changes

• docs: move ADMIN_SAFE_INTEGRATION_PLAN.md to utils (4167234)

0.5.0 (2025-06-09)

Features

• add minimum upload size validation and improve storage reliability (4270590)
• storage: add creation callbacks and remove out-of-scope methods (2de7f91)
• storage: implement download method and simplify DownloadOptions (05c1b79)
• storage: implement preflight checks and refactor allowance API (2746cba)
• storage: implement provider selection and proof set management (9faf04f)
• storage: implement upload method with UploadCallbacks (e289ae9)

Bug Fixes

• add hack to skip 60s delay in upload during tests (f4ade39)
• docs: update README examples for latest signatures (b574a90)
• pdp: restore correct upload protocol with check object (18618b2)
• semantic-release bug (bf340d8)

Trivial Changes

• remove example-usage.js in favour of new examples in utils/ (72dbe23)
• remove unused getters (1bed0db)
• use ethers.js utilities instead of hardcoded decimals (8895422)

... (truncated)

Commits

• e5789b9 chore(release): 0.7.0 [skip ci]
• 8433899 feat(storage): implement smart provider selection to prefer existing relation...
• f2023b1 chore(release): 0.6.1 [skip ci]
• fecfaa5 chore(deps-dev): bump @​types/node from 22.15.31 to 24.0.0
• d6c2fd9 doc: minor tool updates in utils
• b0ffabe chore(release): 0.6.0 [skip ci]
• 4167234 chore(docs): move ADMIN_SAFE_INTEGRATION_PLAN.md to utils
• 353551a fix: remove 60s delay after createproofset and associated testing hack
• e6a79bc feat(utils): add Pandora storage provider admin portal [skip ci] (#79)
• 2482e2c chore(release): 0.5.0 [skip ci]
• Additional commits viewable in compare view

Updates @nestjs/common from 11.1.13 to 11.1.28

Release notes

Sourced from @​nestjs/common's releases.

v11.1.28 (2026-07-08)

Bug fixes

• core
  • #17239 fix(core): trigger teardown of SSE producer Observable on client disconnect with interceptor (@​jyx-07)
• common
  • #17257 fix(common): Add missing exception classes to HttpErrorByCode (@​Se3do)
• websockets
  • #17188 fix(websockets): correct type guard to check value not key (@​Se3do)

Enhancements

• core
  • #17241 feat(core): include auto-converted route in legacy route path warning (@​ronielli)

Dependencies

• platform-fastify
  • #17262 chore(deps): bump fastify from 5.8.5 to 5.10.0 (@​dependabot[bot])
• platform-express
  • #17164 fix(deps): update dependency multer to v2.2.0 [security] (@​renovate[bot])

Committers: 4

• Mohammed Said (@​Se3do)
• Ronielli (@​ronielli)
• greymoth (@​greymoth-jp)
• 종윤 (@​jyx-07)

v11.1.27

What's Changed

• fix(core): sse async handlers teardown issue by @​kamilmysliwiec in nestjs/nest#17131
• fix(platform-fastify): forRoutes middleware ending slash by @​kamilmysliwiec in nestjs/nest#17138

Full Changelog: nestjs/nest@v11.1.26...v11.1.27

v11.1.26

What's Changed

• fix(core): post sse endpoint empty response #17098 by @​kamilmysliwiec in nestjs/nest#17099

Full Changelog: nestjs/nest@v11.1.25...v11.1.26

v11.1.25

What's Changed

• fix(microservices): reject pending Redis requests on close by @​yudin-s in nestjs/nest#17024
• fix(core): register SSE close listener before async setup by @​fallintoplace in nestjs/nest#17018
• fix(platform-fastify): remove pathname ending slash by @​kamilmysliwiec in nestjs/nest#17094

New Contributors

• @​fallintoplace made their first contribution in nestjs/nest#17018
• @​DucMinhNe made their first contribution in nestjs/nest#17085

... (truncated)

Commits

• dfaa376 chore(release): publish v11.1.28 release
• a5e86d8 fix(common): Add missing exception classes to HttpErrorByCode
• 660a124 chore(release): publish v11.1.27 release
• aa5c4f1 chore: update readme and package.json
• 9ff83d5 chore(release): publish v11.1.26 release
• 02f8041 chore(release): publish v11.1.25 release
• 1634915 test(common): Add unit tests for cli-colors utility
• 380bf5c Merge pull request #17058 from Se3do/test/extend-metadata
• af4542b test(common): Add unit tests for assignCustomParameterMetadata
• b67aea1 test(common): Add unit tests for extendArrayMetadata
• Additional commits viewable in compare view

Updates @nestjs/config from 4.0.3 to 4.0.4

Release notes

Sourced from @​nestjs/config's releases.

Release 4.0.4

• fix(deps): update dependency dotenv to v17.4.1 (6bc5737)
• fix(deps): update dependency lodash to v4.18.1 [security] (f31ee98)

Commits

• 3b5d592 chore(): release v4.0.4
• 4fbcb03 Merge pull request #2263 from nestjs/renovate/dotenv-17.x
• 33dae89 Merge pull request #2269 from nestjs/renovate/cimg-node-24.x
• 0a727c3 Merge pull request #2313 from nestjs/renovate/npm-lodash-vulnerability
• 6bc5737 fix(deps): update dependency dotenv to v17.4.1
• f31ee98 fix(deps): update dependency lodash to v4.18.1 [security]
• 059314c chore(deps): update dependency typescript-eslint to v8.58.1 (#2315)
• 0f81e2d chore(deps): update dependency eslint to v10.2.0 (#2314)
• e673ab2 chore(deps): update dependency @​types/node to v24.12.2 (#2311)
• b1ede30 chore(deps): update nest monorepo to v11.1.18 (#2312)
• Additional commits viewable in compare view

Updates @nestjs/core from 11.1.13 to 11.1.28

Release notes

Sourced from @​nestjs/core's releases.

v11.1.28 (2026-07-08)

Bug fixes

• core
  • #17239 fix(core): trigger teardown of SSE producer Observable on client disconnect with interceptor (@​jyx-07)
• common
  • #17257 fix(common): Add missing exception classes to HttpErrorByCode (@​Se3do)
• websockets
  • #17188 fix(websockets): correct type guard to check value not key (@​Se3do)

Enhancements

• core
  • #17241 feat(core): include auto-converted route in legacy route path warning (@​ronielli)

Dependencies

• platform-fastify
  • #17262 chore(deps): bump fastify from 5.8.5 to 5.10.0 (@​dependabot[bot])
• platform-express
  • #17164 fix(deps): update dependency multer to v2.2.0 [security] (@​renovate[bot])

Committers: 4

• Mohammed Said (@​Se3do)
• Ronielli (@​ronielli)
• greymoth (@​greymoth-jp)
• 종윤 (@​jyx-07)

v11.1.27

What's Changed

• fix(core): sse async handlers teardown issue by @​kamilmysliwiec in nestjs/nest#17131
• fix(platform-fastify): forRoutes middleware ending slash by @​kamilmysliwiec in nestjs/nest#17138

Full Changelog: nestjs/nest@v11.1.26...v11.1.27

v11.1.26

What's Changed

• fix(core): post sse endpoint empty response #17098 by @​kamilmysliwiec in nestjs/nest#17099

Full Changelog: nestjs/nest@v11.1.25...v11.1.26

v11.1.25

What's Changed

• fix(microservices): reject pending Redis requests on close by @​yudin-s in nestjs/nest#17024
• fix(core): register SSE close listener before async setup by @​fallintoplace in nestjs/nest#17018
• fix(platform-fastify): remove pathname ending slash by @​kamilmysliwiec in nestjs/nest#17094

New Contributors

• @​fallintoplace made their first contribution in nestjs/nest#17018
• @​DucMinhNe made their first contribution in nestjs/nest#17085

... (truncated)

Commits

• dfaa376 chore(release): publish v11.1.28 release
• 053a316 Merge pull request #17239 from jyx-07/fix/sse-interceptor-teardown
• 8e7a2ee feat(core): include auto-converted route in legacy route path warning
• c5b7164 fix(core): trigger sse observable teardown on disconnect
• 660a124 chore(release): publish v11.1.27 release
• 5c5e9ba fix(core): sse async handlers teardown issue #17128
• aa5c4f1 chore: update readme and package.json
• 9ff83d5 chore(release): publish v11.1.26 release
• 0f398fd test: fix broken unit test
• d152eec fix(core): post sse endpoint empty response #17098
• Additional commits viewable in compare view

Updates @nestjs/platform-express from 11.1.13 to 11.1.28

Release notes

Sourced from @​nestjs/platform-express's releases.

v11.1.28 (2026-07-08)

Bug fixes

• core
  • #17239 fix(core): trigger teardown of SSE producer Observable on client disconnect with interceptor (@​jyx-07)
• common
  • #17257 fix(common): Add missing exception classes to HttpErrorByCode (@​Se3do)
• websockets
  • #17188 fix(websockets): correct type guard to check value not key (@​Se3do)

Enhancements

• core
  • #17241 feat(core): include auto-converted route in legacy route path warning (@​ronielli)

Dependencies

• platform-fastify
  • #17262 chore(deps): bump fastify from 5.8.5 to 5.10.0 (@​dependabot[bot])
• platform-express
  • #17164 fix(deps): update dependency multer to v2.2.0 [security] (@​renovate[bot])

Committers: 4

• Mohammed Said (@​Se3do)
• Ronielli (@​ronielli)
• greymoth (@​greymoth-jp)
• 종윤 (@​jyx-07)

v11.1.27

What's Changed

• fix(core): sse async handlers teardown issue by @​kamilmysliwiec in nestjs/nest#17131
• fix(platform-fastify): forRoutes middleware ending slash by @​kamilmysliwiec in nestjs/nest#17138

Full Changelog: nestjs/nest@v11.1.26...v11.1.27

v11.1.26

What's Changed

• fix(core): post sse endpoint empty response #17098 by @​kamilmysliwiec in nestjs/nest#17099

Full Changelog: nestjs/nest@v11.1.25...v11.1.26

v11.1.25

What's Changed

• fix(microservices): reject pending Redis requests on close by @​yudin-s in nestjs/nest#17024
• fix(core): register SSE close listener before async setup by @​fallintoplace in nestjs/nest#17018
• fix(platform-fastify): remove pathname ending slash by @​kamilmysliwiec in nestjs/nest#17094

New Contributors

• @​fallintoplace made their first contribution in nestjs/nest#17018
• @​DucMinhNe made their first contribution in nestjs/nest#17085

... (truncated)

Commits

• dfaa376 chore(release): publish v11.1.28 release
• 541977a fix(deps): update dependency multer to v2.2.0 [security]
• 660a124 chore(release): publish v11.1.27 release
• aa5c4f1 chore: update readme and package.json
• 9ff83d5 chore(release): publish v11.1.26 release
• 02f8041 chore(release): publish v11.1.25 release
• d8a0ab8 chore(release): publish v11.1.24 release
• 2dccece chore: update readmes
• b8be8c1 chore(release): publish v11.1.23 release
• 801c46f chore(release): publish v11.1.22 release
• Additional commits viewable in compare view

Updates @nestjs/schedule from 6.1.1 to 6.1.3

Release notes

Sourced from @​nestjs/schedule's releases.

6.1.3

What's Changed

• feat(cron): add initialDelay option to defer first job execution by @​kyungseopk1m in nestjs/schedule#2251

Full Changelog: nestjs/schedule@6.1.2...6.1.3

Release 6.1.2

• Merge pull request #2247 from kyungseopk1m/feat/cron-initial-delay (a57ce2c)
• chore(deps): update dependency prettier to v3.8.3 (#2248) (bb3490d)
• feat(cron): add initialDelay option to defer first job execution (1c5677f)
• Merge pull request #2245 from nestjs/renovate/nest-monorepo (59046bd)
• Merge pull request #2246 from nestjs/renovate/oxlint-monorepo (be4eee3)
• chore(deps): update dependency oxlint to v1.60.0 (32a9ce2)
• chore(deps): update nest monorepo to v11.1.19 (7d3844f)
• chore: migrate to oxlint, vitest, ts6 (29de71b)
• chore(deps): update dependency globals to v17.5.0 (#2244) (6c62cca)
• chore(deps): update dependency sinon to v21.1.2 (#2243) (ee3b31a)
• chore(deps): update dependency sinon to v21.1.1 (#2241) (eba9799)
• Merge pull request #2242 from nestjs/renovate/prettier-3.x (c3ad0f7)
• chore(deps): update dependency prettier to v3.8.2 (798e2a9)
• Merge pull request #2199 from nestjs/renovate/cimg-node-24.x (a05354a)
• chore(deps): update dependency typescript-eslint to v8.58.1 (#2240) (0367ac1)
• chore(deps): update dependency eslint to v10.2.0 (#2239) (fa93e06)
• chore(deps): update nest monorepo to v11.1.18 (#2238) (8cd4c02)
• chore(deps): update dependency @​types/node to v24.12.2 (#2237) (01482df)
• chore(deps): update dependency @​types/sinon to v21.0.1 (#2236) (f05b5bd)
• chore(deps): update dependency ts-jest to v29.4.9 (#2235) (af545e6)
• chore(deps): update dependency typescript-eslint to v8.58.0 (#2233) (4dad22a)
• chore(deps): update node.js to v24.14.1 (28db9bc)
• chore(deps): update dependency eslint to v10.1.0 (#2232) (413f390)
• chore(deps): update nest monorepo to v11.1.17 (#2230) (46c2bc5)
• chore(deps): update dependency typescript-eslint to v8.57.1 (#2231) (8fd063b)
• chore(deps): update dependency sinon to v21.0.3 (#2229) (1671ad9)
• chore(deps): update commitlint monorepo to v20.5.0 (#2228) (2ecd2f1)
• chore(deps): update dependency lint-staged to v16.4.0 (#2227) (aa0de01)
• chore(deps): update commitlint monorepo to v20.4.4 (#2226) (75034fe)
• chore(deps): update dependency lint-staged to v16.3.3 (#2225) (f1c7d31)
• chore(deps): update dependency jest to v30.3.0 (#2224) (1a208d4)
• chore(deps): update dependency typescript-eslint to v8.57.0 (<...

  Description has been truncated

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​nestjs/​schematics@​11.1.0
	react-router-dom@​7.18.1
	@​radix-ui/​react-slot@​1.2.3 ⏵ 1.3.3	+1		+1
	@​radix-ui/​react-tabs@​1.1.21
	@​radix-ui/​react-switch@​1.3.7
	@​types/​react@​19.2.17
	@​vitest/​coverage-v8@​4.1.10
	vitest@​4.1.10
	joi@​18.2.3
	recharts@​3.10.1
	lucide-react@​1.27.0
	@​willsoto/​nestjs-prometheus@​6.1.0
	@​filoz/​synapse-core@​0.7.0
	tailwindcss@​4.3.3
	react@​19.2.8
	class-validator@​0.15.1
	helmet@​8.3.0
	@​nestjs/​schedule@​6.1.3
	@​nestjs/​typeorm@​11.0.3
	@​nestjs/​cli@​11.0.24
	@​nestjs/​config@​4.0.4
	tailwind-merge@​3.6.0
	date-fns@​4.4.0
	pg@​8.22.0
	@​nestjs/​swagger@​11.4.6
	@​tailwindcss/​vite@​4.3.3
	assemblyscript@​0.28.20
	axios@​1.18.1
	react-dom@​19.2.8
	@​swc/​core@​1.15.46
	multiformats@​14.0.5
	ts-loader@​9.6.2
	swr@​2.4.2
See 7 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		Obfuscated code: npm @mswjs/interceptors is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/vitest@4.1.10 → npm/msw@2.15.0 → npm/@mswjs/interceptors@0.41.9 ℹ Read more on: This package | This alert | What is obfuscated code? 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: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@mswjs/interceptors@0.41.9. 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		Obfuscated code: npm strtok3 is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/@nestjs/common@11.1.28 → npm/strtok3@10.3.5 ℹ Read more on: This package | This alert | What is obfuscated code? 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: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/strtok3@10.3.5. 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		Obfuscated code: npm validator is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/class-validator@0.15.1 → npm/validator@13.15.35 ℹ Read more on: This package | This alert | What is obfuscated code? 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: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/validator@13.15.35. 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		Obfuscated code: npm webpack is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/ts-loader@9.6.2 → npm/@nestjs/cli@11.0.24 → npm/webpack@5.106.2 ℹ Read more on: This package | This alert | What is obfuscated code? 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: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/webpack@5.106.2. 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		Obfuscated code: npm yargs is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/vitest@4.1.10 → npm/msw@2.15.0 → npm/yargs@17.7.3 ℹ Read more on: This package | This alert | What is obfuscated code? 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: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/yargs@17.7.3. 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