[dependabot]

Bumps the npm-production group with 18 updates in the / directory:

Package	From	To
@opentelemetry/exporter-metrics-otlp-http	0.222.0	0.223.0
express	5.2.1	5.3.0
fastify	5.12.5	5.12.7
@hono/node-server	2.1.3	2.1.5
hono	4.13.12	4.13.13
@vue/server-renderer	3.5.43	3.5.44
vue	3.5.43	3.5.44
react	19.3.0	19.3.1
react-dom	19.3.0	19.3.1
@nestjs/common	12.1.2	12.1.3
@nestjs/core	12.1.2	12.1.3
@nestjs/platform-express	12.1.2	12.1.3
@nestjs/platform-fastify	12.1.2	12.1.3
@types/node	26.6.4	26.6.5
@vitest/coverage-v8	5.0.3	5.0.5
tsdown	0.23.0	0.23.1
vite	8.3.2	8.3.4
vitest	5.0.3	5.0.5

Updates @opentelemetry/exporter-metrics-otlp-http from 0.222.0 to 0.223.0

Release notes

Sourced from @​opentelemetry/exporter-metrics-otlp-http's releases.

experimental/v0.223.0

0.223.0

💥 Breaking Changes

• chore(web-common)!: clean up and deprecate network span utils #7114
  • These utilities were long planned for removal. They were moved from the sdk-trace-web package and are currently only used by the (deprecated) instrumentation-fetch and instrumentation-xml-http-request packages.
  • Drop the skipOldSemconvContentLengthAttrs vestigial option from addSpanNetworkEvents().

🏠 Internal

• refactor(web-common, instrumentation-fetch, instrumentation-xml-http-request): move utils from @opentelemetry/sdk-trace-web into @opentelemetry/web-common and use them in @opentelemetry/instrumentation-fetch and @opentelemetry/instrumentation-xml-http-request. With this change the instrumentations do not depend on SDK packages and the utils are kept in a shared package so we avoid code duplication.

Commits

• 92b844e chore: prepare next v2.x release (#7151)
• a859aff fix(web-common): export getElementXPath utility (#7124)
• 2bd5a73 chore(web-common)!: deprecate addSpanNetworkEvents() et al instrumentation-...
• d60f05e doc(sdk-trace): add description for StackContextManager (#7089)
• 5bd476e chore: move context manager to sdk-trace (#7086)
• 554c0c6 chore: move sdk-trace-web utils to web-common (#7058)
• 788922c ci: support maintenance branch releases (#7036)
• See full diff in compare view

Updates express from 5.2.1 to 5.3.0

Release notes

Sourced from express's releases.

v5.3.0

Highlights

🐞 Bug fixes

• Fixed HTTP header conflict between Content-Length and Transfer-Encoding in res.send - by @​YuryShkoda in #4893

  Fixed the behavior of res.send() to prevent conflicts between Content-Length and Transfer-Encoding HTTP headers in responses. The Content-Length header in res.send() is now only added when a Transfer-Encoding header is not present, complying with the HTTP specification that states both headers should not coexist in the same response. ETag generation is unaffected by the presence of a Transfer-Encoding header - by @​cuishuang in #7459

• Upgrade qs to ^6.16.0, which fixes CVE-2026-2391 (GHSA-w7fw-mjwx-w883), CVE-2026-82417 (GHSA-4mjr-xmp4-gh2g) and CVE-2026-82562 (GHSA-x5fp-wj9c-mxmx): arrayLimit bypasses in comma parsing and a denial of service via an attacker-controlled isBuffer - by @​davetashner in #7057 and #7478, and @​cyphercodes in #7305

• Upgrade proxy-addr to ^2.0.8, which fixes CVE-2026-90711 - by @​lazerg in #7474

🚀 Improvements

• Allow conditional revalidation for QUERY requests. req.fresh previously only validated freshness for GET and HEAD requests, so QUERY responses never returned 304 despite a matching validator. Since QUERY is a safe, idempotent, and cacheable method that supports conditional requests, it is now included in the freshness check - by @​Cherry in #7366

  // QUERY /reports with If-None-Match: "12345"
  app.query('/reports', (req, res) => {
    res.set('ETag', '"12345"');
    res.send(results); // now responds 304 Not Modified
  });

• Improve HTML structure in res.redirect() responses when HTML format is accepted by adding <!DOCTYPE html>, <title>, and <body> tags for better browser compatibility - by @​Bernice55231 in #5167

• When calling app.render with options set to null, the locals object is handled correctly, preventing unexpected errors and making the method behave the same as when options is omitted or an empty object is passed - by AkaHarshit in #6903

  app.render('index', null, callback); // now works as expected

• Upgrade content-type to ^2.0.0, bringing a faster parser (~1.5x quicker Content-Type parsing/formatting in res.send()) along with a behavior change: res.send() now keeps any existing parameters when adding the charset and no longer throws on a Content-Type that fails to parse. type-is is upgraded to ^2.1.0 as part of the same change - by @​blakeembrey in #7234

  res.set('Content-Type', 'text/plain; foo=bar').send('hey');
  // -> Content-Type: text/plain; foo=bar; charset=utf-8

• The default error handler now logs the full error object instead of only its stack trace, so nested details such as Error.cause and library-specific properties (e.g. Sequelize's parent/original) are no longer swallowed - by @​Nitin-Mohapatra in #6464

• Upgrade content-disposition to ^2.0.1, which changes the Content-Disposition header emitted by res.download(), res.attachment(), and res.sendFile(): file names that are valid HTTP tokens are no longer wrapped in quotes. This is equivalent per RFC 6266, but applications asserting on the exact header bytes should update their expectations - by @​blakeembrey in #7233

  res.attachment('user.html');
  // before -> Content-Disposition: attachment; filename="user.html"
  // after  -> Content-Disposition: attachment; filename=user.html

... (truncated)

Changelog

Sourced from express's changelog.

5.3.0

🐞 Bug fixes

• Fixed HTTP header conflict between Content-Length and Transfer-Encoding in res.send - by @​YuryShkoda in #4893

  Fixed the behavior of res.send() to prevent conflicts between Content-Length and Transfer-Encoding HTTP headers in responses. The Content-Length header in res.send() is now only added when a Transfer-Encoding header is not present, complying with the HTTP specification that states both headers should not coexist in the same response. ETag generation is unaffected by the presence of a Transfer-Encoding header - by @​cuishuang in #7459

• Upgrade qs to ^6.16.0, which fixes CVE-2026-2391 (GHSA-w7fw-mjwx-w883), CVE-2026-82417 (GHSA-4mjr-xmp4-gh2g) and CVE-2026-82562 (GHSA-x5fp-wj9c-mxmx): arrayLimit bypasses in comma parsing and a denial of service via an attacker-controlled isBuffer - by @​davetashner in #7057 and #7478, and @​cyphercodes in #7305

• Upgrade proxy-addr to ^2.0.8, which fixes CVE-2026-90711 - by @​lazerg in #7474

🚀 Improvements

• Allow conditional revalidation for QUERY requests. req.fresh previously only validated freshness for GET and HEAD requests, so QUERY responses never returned 304 despite a matching validator. Since QUERY is a safe, idempotent, and cacheable method that supports conditional requests, it is now included in the freshness check - by @​Cherry in #7366

  // QUERY /reports with If-None-Match: "12345"
  app.query('/reports', (req, res) => {
    res.set('ETag', '"12345"');
    res.send(results); // now responds 304 Not Modified
  });

• Improve HTML structure in res.redirect() responses when HTML format is accepted by adding <!DOCTYPE html>, <title>, and <body> tags for better browser compatibility - by @​Bernice55231 in #5167

• When calling app.render with options set to null, the locals object is handled correctly, preventing unexpected errors and making the method behave the same as when options is omitted or an empty object is passed - by AkaHarshit in #6903

  app.render('index', null, callback); // now works as expected

• Upgrade content-type to ^2.0.0, bringing a faster parser (~1.5x quicker Content-Type parsing/formatting in res.send()) along with a behavior change: res.send() now keeps any existing parameters when adding the charset and no longer throws on a Content-Type that fails to parse. type-is is upgraded to ^2.1.0 as part of the same change - by @​blakeembrey in #7234

  res.set('Content-Type', 'text/plain; foo=bar').send('hey');
  // -> Content-Type: text/plain; foo=bar; charset=utf-8

• The default error handler now logs the full error object instead of only its stack trace, so nested details such as Error.cause and library-specific properties (e.g. Sequelize's parent/original) are no longer swallowed - by @​Nitin-Mohapatra in #6464

• Upgrade content-disposition to ^2.0.1, which changes the Content-Disposition header emitted by res.download(), res.attachment(), and res.sendFile(): file names that are valid HTTP tokens are no longer wrapped in quotes. This is equivalent per RFC 6266, but applications asserting on the exact header bytes should update their expectations - by @​blakeembrey in #7233

  res.attachment('user.html');
  // before -> Content-Disposition: attachment; filename="user.html"
  // after  -> Content-Disposition: attachment; filename=user.html

... (truncated)

Commits

• cf6722b 5.3.0 (#7468)
• 8c2fcfc docs: fix typos and a stale API reference in lib comments (#7512)
• 9efc29e docs: fix pass-through typos (#7509)
• 2717ae3 build(deps): bump the github-actions group with 3 updates (#7499)
• de77771 build(deps-dev): bump hbs from 4.3.0 to 4.3.1 (#7500)
• 9169cbe docs: add missing apostrophe in example (#7483)
• 7ef9844 build(deps-dev): bump morgan from 1.12.0 to 1.12.1 (#7493)
• 3b7e39f deps: bump qs minimum to 6.16.0 (#7478)
• 98bd4cd deps: proxy-addr@^2.0.8 (#7474)
• 9a34acf fix(res.send): preserve ETag generation with Transfer-Encoding (#7459)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for express since your current version.

Updates fastify from 5.12.5 to 5.12.7

Release notes

Sourced from fastify's releases.

v5.12.7

Full Changelog: fastify/fastify@v5.12.6...v5.12.7

v5.12.6

⚠️ Security Release

• Fix for GHSA-389g-gv7q-r4x8

What's Changed

• [Backport 5.x] types: restrict route lookup methods by @​github-actions[bot] in fastify/fastify#7048
• [Backport 5.x] perf: decode string bodies once instead of per chunk by @​github-actions[bot] in fastify/fastify#7053
• [Backport 5.x] perf: avoid resetting the level of request child loggers by @​github-actions[bot] in fastify/fastify#7058
• [Backport 5.x] fix: resolve reply.mediaType from raw response headers by @​github-actions[bot] in fastify/fastify#7067
• [Backport 5.x] perf: use a FIFO cache for parsed content-types by @​github-actions[bot] in fastify/fastify#7072
• [Backport 5.x] fix(validation): lowercase header names in propertyNames enum/const by @​mcollina in fastify/fastify#7104
• [Backport 5.x] fix: copy a set-cookie array passed to reply.header instead of storing it by @​github-actions[bot] in fastify/fastify#7087
• [Backport 5.x] fix: remove error when HTTP QUERY request has empty body by @​github-actions[bot] in fastify/fastify#7060
• [Backport 5.x] docs: document fastify.query() shorthand for RFC 10008 by @​github-actions[bot] in fastify/fastify#7094

Full Changelog: fastify/fastify@v5.12.5...v5.12.6

Commits

• 9f40003 Bumped v5.12.7
• 16469b9 Bumped v5.12.6
• 63496de [Backport 5.x] docs: document fastify.query() shorthand for RFC 10008 (#7094)
• 20b55d4 [Backport 5.x] fix: remove error when HTTP QUERY request has empty body (#7060)
• 38d2b63 [Backport 5.x] fix: copy a set-cookie array passed to reply.header instead of...
• 3241fbd [Backport 5.x] fix(validation): lowercase header names in propertyNames enum/...
• 1a46b1b [Backport 5.x] perf: use a FIFO cache for parsed content-types (#7072)
• 7e06676 [Backport 5.x] fix: resolve reply.mediaType from raw response headers (#7067)
• 1b0eb32 [Backport 5.x] perf: avoid resetting the level of request child loggers (#7058)
• a636a10 [Backport 5.x] perf: decode string bodies once instead of per chunk (#7053)
• Additional commits viewable in compare view

Updates @hono/node-server from 2.1.3 to 2.1.5

Release notes

Sourced from @​hono/node-server's releases.

v2.1.5

What's Changed

• fix(listener): abort the request signal when an HTTP/2 client resets the stream by @​affanmomin in honojs/node-server#404
• fix(serve-static): only serve GET and HEAD requests by @​usualoma in honojs/node-server#405

New Contributors

• @​affanmomin made their first contribution in honojs/node-server#404

Full Changelog: honojs/node-server@v2.1.4...v2.1.5

v2.1.4

What's Changed

• chore: allow hono v5 as a peer dependency by @​yusukebe in honojs/node-server#406

Full Changelog: honojs/node-server@v2.1.3...v2.1.4

Commits

• 4b47a0d 2.1.5
• e77824a fix(serve-static): only serve GET and HEAD requests (#405)
• 1b6e6bf fix(listener): abort the request signal when an HTTP/2 client resets the stre...
• d57ed9b 2.1.4
• 92b014c chore: allow hono v5 as a peer dependency (#406)
• See full diff in compare view

Updates hono from 4.13.12 to 4.13.13

Release notes

Sourced from hono's releases.

v4.13.13

Mount Middleware

app.mount() is now available as the Mount Middleware, hono/mount. It is just a handler, so you register it with app.all():

import { Router as IttyRouter } from 'itty-router'
import { Hono } from 'hono'
import { mount } from 'hono/mount'
const ittyRouter = IttyRouter()
ittyRouter.get('/hello', () => new Response('Hello from itty-router'))
const app = new Hono()
app.all('/itty-router/*', mount(ittyRouter.handle))

app.mount() still works in v4 but is deprecated and will be removed in v5. Migrating is a one-line change:

- app.mount('/itty-router', ittyRouter.handle)
+ app.all('/itty-router/*', mount(ittyRouter.handle))

What's Changed

• test(client): simulate network error for undefined route in parseResponse test in honojs/hono#5439
• docs(request): fix jsdoc comments for some getters in honojs/hono#5445
• fix(jsx): allow JSXNode function component results in honojs/hono#5476
• feat(mount): introduce Mount Middleware and deprecate app.mount in honojs/hono#5221

Full Changelog: honojs/hono@v4.13.12...v4.13.13

Commits

• 08a023c 4.13.13
• ae595de feat(mount): introduce Mount Middleware and deprecate app.mount (#5221)
• f23b146 fix(jsx): allow JSXNode function component results (#5476)
• 6d73a74 docs(request): fix jsdoc comments for some getters (#5445)
• deff529 test(client): simulate network error for undefined route in parseResponse tes...
• See full diff in compare view

Updates @vue/server-renderer from 3.5.43 to 3.5.44

Release notes

Sourced from @​vue/server-renderer's releases.

v3.5.44

For stable releases, please refer to CHANGELOG.md for details. For pre-releases, please refer to CHANGELOG.md of the minor branch.

Changelog

Sourced from @​vue/server-renderer's changelog.

3.5.44 (2026-10-13)

Bug Fixes

• compat: expose _setupProxy for Vue 2.7 compiled script setup (fix #11164) (#15618) (f08059d)
• compiler-core: parenthesise v-for key in v-memo cache guard (#15724) (d084b90), closes #15723
• compiler-dom: correctly stringify 0 and false in v-html (#15571) (9f3b437)
• compiler-dom: inject transition persisted for v-show in production (#15783) (89cb272)
• compiler-sfc: error when defineModel prop options reference a destructured prop (#15604) (38012a5), closes #15602
• custom-element: skip mounting an async custom element removed while its component loads (#15777) (0f8e7b4), closes #15775
• hydration: observe children of a display: contents root in hydrateOnVisible (#15773) (7f688e8)
• KeepAlive: unmount pruned current component when its vnode was cloned on mount (#15711) (92798ac), closes #15710
• reactivity: avoid mutating native array iterators (#15703) (7f9d45d), closes #15643
• reactivity: do not track deps in watcher callbacks run inside another effect (#15782) (db00fe9), closes #5009
• reactivity: once watcher should stop when its callback throws (#15755) (ae4bd94)
• reactivity: preserve shallow collection semantics (#15793) (b600466), closes #15792
• runtime-core: detect new prop keys when comparing full props (#15634) (702fa61), closes #15632
• runtime-core: keep async placeholder for block patching and pending component updates (#15554) (05ec25f), closes #15551
• runtime-core: only flush jobs queued by the root render itself (#15757) (0bea14b), closes #6728
• runtime-core: render nothing for an invalid v-for range in production (#15742) (ad19e7d)
• runtime-dom: preserve v-show display for unchanged style strings (#15794) (c0a6d3f)
• runtime-dom: treat playsinline as a boolean attribute (#15627) (a084e44)
• server-renderer: propagate async setup errors (#15857) (6930374), closes #15716
• ssr: honor falsy vnode content overrides (#15769) (c11c5c8)
• suspense: mount resolved async component with its own namespace (#15640) (2a086a2), closes #15639
• suspense: skip rendering async components unmounted while pending (4ab865a)
• teleport: move targetStart and keep children before targetAnchor (#15818) (d3c6e02), closes #15817
• transition-group: measure nested groups against their moving outer item (#15848) (1936c87), closes #5385 #1531
• transition: handle comment-wrapped component roots (#15853) (ff35014), closes #6080 #5500

Commits

• bf5f0dd release: v3.5.44
• 6930374 fix(server-renderer): propagate async setup errors (#15857)
• c11c5c8 fix(ssr): honor falsy vnode content overrides (#15769)
• ad19e7d fix(runtime-core): render nothing for an invalid v-for range in production (#...
• a084e44 fix(runtime-dom): treat playsinline as a boolean attribute (#15627)
• See full diff in compare view

Updates vue from 3.5.43 to 3.5.44

Release notes

Sourced from vue's releases.

v3.5.44

For stable releases, please refer to CHANGELOG.md for details. For pre-releases, please refer to CHANGELOG.md of the minor branch.

Changelog

Sourced from vue's changelog.

3.5.44 (2026-10-13)

Bug Fixes

• compat: expose _setupProxy for Vue 2.7 compiled script setup (fix #11164) (#15618) (f08059d)
• compiler-core: parenthesise v-for key in v-memo cache guard (#15724) (d084b90), closes #15723
• compiler-dom: correctly stringify 0 and false in v-html (#15571) (9f3b437)
• compiler-dom: inject transition persisted for v-show in production (#15783) (89cb272)
• compiler-sfc: error when defineModel prop options reference a destructured prop (#15604) (38012a5), closes #15602
• custom-element: skip mounting an async custom element removed while its component loads (#15777) (0f8e7b4), closes #15775
• hydration: observe children of a display: contents root in hydrateOnVisible (#15773) (7f688e8)
• KeepAlive: unmount pruned current component when its vnode was cloned on mount (#15711) (92798ac), closes #15710
• reactivity: avoid mutating native array iterators (#15703) (7f9d45d), closes #15643
• reactivity: do not track deps in watcher callbacks run inside another effect (#15782) (db00fe9), closes #5009
• reactivity: once watcher should stop when its callback throws (#15755) (ae4bd94)
• reactivity: preserve shallow collection semantics (#15793) (b600466), closes #15792
• runtime-core: detect new prop keys when comparing full props (#15634) (702fa61), closes #15632
• runtime-core: keep async placeholder for block patching and pending component updates (#15554) (05ec25f), closes #15551
• runtime-core: only flush jobs queued by the root render itself (#15757) (0bea14b), closes #6728
• runtime-core: render nothing for an invalid v-for range in production (#15742) (ad19e7d)
• runtime-dom: preserve v-show display for unchanged style strings (#15794) (c0a6d3f)
• runtime-dom: treat playsinline as a boolean attribute (#15627) (a084e44)
• server-renderer: propagate async setup errors (#15857) (6930374), closes #15716
• ssr: honor falsy vnode content overrides (#15769) (c11c5c8)
• suspense: mount resolved async component with its own namespace (#15640) (2a086a2), closes #15639
• suspense: skip rendering async components unmounted while pending (4ab865a)
• teleport: move targetStart and keep children before targetAnchor (#15818) (d3c6e02), closes #15817
• transition-group: measure nested groups against their moving outer item (#15848) (1936c87), closes #5385 #1531
• transition: handle comment-wrapped component roots (#15853) (ff35014), closes #6080 #5500

Commits

• bf5f0dd release: v3.5.44
• 6930374 fix(server-renderer): propagate async setup errors (#15857)
• 8e8c547 chore(deps): update all non-major dependencies (#15585)
• 4cb0ca8 chore(deps): update playground (#15685)
• e38478f chore(deps): update dawidd6/action-download-artifact action to v27 (#15768)
• 1caed5a chore(deps): update compiler (#15586)
• a49f451 chore(deps): update lint (#15680)
• 219b858 chore(deps): update build (#15679)
• ff35014 fix(transition): handle comment-wrapped component roots (#15853)
• d084b90 fix(compiler-core): parenthesise v-for key in v-memo cache guard (#15724)
• Additional commits viewable in compare view

Updates react from 19.3.0 to 19.3.1

Release notes

Sourced from react's releases.

19.3.1 (October 14th, 2026)

React Server Components

• Improve transport protocol (#37845 by @​unstubbable and @​eps1lon)

Commits

• 61aa00d [19.3.x][Flight] Improve transport protocol (#37845)
• See full diff in compare view

Updates react-dom from 19.3.0 to 19.3.1

Release notes

Sourced from react-dom's releases.

19.3.1 (October 14th, 2026)

React Server Components

• Improve transport protocol (#37845 by @​unstubbable and @​eps1lon)

Commits

• 61aa00d [19.3.x][Flight] Improve transport protocol (#37845)
• See full diff in compare view

Updates @nestjs/common from 12.1.2 to 12.1.3

Release notes

Sourced from @​nestjs/common's releases.

v12.1.3 (2026-10-12)

Bug fixes

• core, microservices
  • #18111 fix(core,microservices): flush buffered logs when initialization fails (@​thekhegay)
  • #17993 fix(core,microservices): run transient global enhancers on controllers (@​johnnyhuirilef)
• platform-express
  • #18110 fix(express): guard async request hook completion (@​GiHoon1123)
  • #17973 fix(express): destroy the StreamableFile source on client disconnect (@​maxymlyskov)
  • #17942 fix(express): run wildcard middleware on the bare global prefix path (@​Chaoqi31)
• core
  • #18104 fix(core): fail at startup for request-scoped class global enhancers (@​thekhegay)
  • #18066 fix(core): stop silently dropping request-scoped global enhancers (@​OmBhandwaldar)
  • #18072 fix(core): resolve uri versioned exclusions for the not-found handler (@​basteez)
  • #18075 fix(core): normalize slashes when mapping controllers for middleware (@​basteez)
  • #18086 fix(core): do not mutate the message when assigning an sse event id (@​Metehan-Bicer)
  • #18025 fix(core): end sse streams whose event data cannot be serialized (@​OmBhandwaldar)
  • #18011 fix(core): send status and headers set by handlers on sse responses (@​johnnyhuirilef)
  • #18021 fix(core): honor a shutdown signal received while close() is in flight (@​maxymlyskov)
  • #17987 fix(core): settle SSE lifecycle on early disconnect (@​jackie-cqz)
  • #17986 fix(core): commit SSE headers for empty streams (@​jackie-cqz)
  • #17978 fix(core): preserve explicit null values in reflectable decorators (@​gophersg)
  • #17966 fix(core): run the shutdown sequence after a failed init (@​kamilmysliwiec)
  • #17963 fix(core): send the expires header on sse responses (@​Mohamed-Elshesheny)
  • #17953 fix(core): honor global prefix exclusions for overlapping versions (@​Chaoqi31)
  • #17950 fix(core): let a GET middleware exclusion cover HEAD requests (@​Chaoqi31)
  • #17951 fix(core): reset the listening state when the application closes (@​Chaoqi31)
  • #17945 fix(core): hash Map, Set and RegExp options in deep-hash tokens (@​Chaoqi31)
  • #17947 fix(core): treat VERSION_NEUTRAL in middleware routes as no version (@​Chaoqi31)
  • #17941 fix(core): turn off express x-powered-by in useSecurityHeaders() (@​Chaoqi31)
  • #17939 fix(core): name dynamic host modules in import error messages (@​Chaoqi31)
  • #17940 fix(core): isolate nested transient providers injected into properties (@​Chaoqi31)
• microservices
  • #18108 fix(microservices): keep nats status updates alive when a listener throws (@​kamilmysliwiec)
  • #18100 fix(microservices): default server options like the client factory does (@​thekhegay)
  • #18083 fix(microservices): match rmq '#' wildcards in any position (@​thekhegay)
  • #18095 fix(microservices): fail mqtt requests whose publish fails (@​izg0820)
  • #18085 fix(microservices): preserve null payloads in kafka tombstone records (@​Hangell)
  • #18081 fix(microservices): close the connection when the channel close fails (@​hktitof)
  • #18071 fix(microservices): return the rmq reply publish so failures are handled (@​maxymlyskov)
  • #18060 fix(microservices): fail redis listen on rejected subscriptions (@​kamilmysliwiec)
  • #18056 fix(microservices): clone the kafka record before serializing (@​Mihir-Rabari)
  • #18054 fix(microservices): do not crash when the redis connection drops (@​maxymlyskov)
  • #18043 fix(microservices): fail pending kafka request on deserializer error (@​hktitof)
  • #18002 fix(microservices): wait for the TCP TLS handshake (@​jackie-cqz)
  • #17995 fix(microservices): survive custom deserializer errors in ...

    Description has been truncated