Skip to content

build(deps): bump the production group with 10 updates - #148

Closed
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/production-2169032fb0
Closed

dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/production-2169032fb0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 16, 2026 •

Copy link
Copy Markdown
Contributor

Bumps the production group with 10 updates:

Package From To
zod 4.6.5 4.6.7
guardagent 3.2.1 3.2.3
fastify-plugin 6.0.0 6.0.1
@fastify/cors 11.3.0 11.3.1
hono 4.13.11 4.13.13
@nestjs/common 12.1.1 12.1.3
@nestjs/core 12.1.1 12.1.3
express 4.22.3 5.3.0
@hono/node-server 2.1.3 2.1.4
@nestjs/platform-express 12.1.1 12.1.3

Updates zod from 4.6.5 to 4.6.7

Release notes

Sourced from zod's releases.

v4.6.7

Commits:

  • b500a2ee95134f81d74da7911d7378dd2853d042 4.6.7

v4.6.6

Six malicious commits pushed to main on September 21 with a compromised git credential were reverted the same day in #6620 and have since been removed from the history of main. None were ever published to npm. The npm provenance for 4.6.6 names 284243fb, the pre-rewrite copy of 9c219833 with identical contents.

Commits:

  • 0cd3af5e9f50ad11bbcd4407a46a21b8848ba574 docs: load the en locale directly in Zod Mini
  • 9d5e60f162997b764b40d45aa02481888db50dea docs: import locales from zod/locales, not z.locales
  • 34a626f307871ecbb0123947559328dc52ed5e3e docs: tighten the z.locales tree-shaking note
  • 74304ce5b5796b5edb9a88ceb8e170b6ea3e82df release: stage npm versions instead of publishing them (#6622)
  • b2ef983e0711ff6517d6020b021071e2e5653efa docs: add Code for Japan to bronze sponsors
  • 8fb2faf0584828a6a027d8279db36f6f52784462 docs: crop the Code for Japan logo and list it first in bronze
  • bacad518c41610d654658172d325874bf0ee6290 docs: square the Code for Japan logo to match the other bronze tiles
  • c42596bd1c87e941d7241d10e012c5c196adcc10 release: hold the run on the release-approval environment until the staged versions are approved (#6638)
  • a2ba4a67986a3e6b2b131be30084a2f460d9ea67 fix(types): declare record output and input as members, not base type arguments (#6645)
  • a0ebf970f2d752e5f58527cd2942ff48be4f46bd fix(v4): check array, set and map size bounds before parsing elements (#6652)
  • 529f78dd9431b07f49647fee3aa0819b3f8b66b7 4.6.6
  • 9c219833c3a3764fa1f1ea9c5ecec8254a63c0b1 ci: stage at verbose so a failed OIDC token exchange says why
Commits
  • b500a2e 4.6.7
  • 9c21983 ci: stage at verbose so a failed OIDC token exchange says why
  • 529f78d 4.6.6
  • a0ebf97 fix(v4): check array, set and map size bounds before parsing elements (#6652)
  • a2ba4a6 fix(types): declare record output and input as members, not base type argumen...
  • c42596b release: hold the run on the release-approval environment until the staged ve...
  • bacad51 docs: square the Code for Japan logo to match the other bronze tiles
  • 8fb2faf docs: crop the Code for Japan logo and list it first in bronze
  • b2ef983 docs: add Code for Japan to bronze sponsors
  • 74304ce release: stage npm versions instead of publishing them (#6622)
  • Additional commits viewable in compare view

Updates guardagent from 3.2.1 to 3.2.3

Release notes

Sourced from guardagent's releases.

v3.2.3 (2026-10-12)

User-Agent identifies the TypeScript agent (v3.2.3)

Changed

  • The ingestion User-Agent header is now guard-agent-ts/<version> (was guardagent/<version>), so the Guard SaaS can tell the TypeScript agent apart from the other ports. Lockstep release with the agent family at 3.2.3.

v3.2.2 (2026-10-09)

Guard-Core org migration metadata release (v3.2.2)

About this release

  • A metadata-only release cut in lockstep with the sibling agents (all five agents at 3.2.2). The guardagent package ships no code changes: the npm package metadata (repository, bugs, homepage) and every repository link moved to the Guard-Core org. Shipped so the agents family moves in lockstep with the engines and the other agent implementations.

Compatibility

  • Drop-in over 3.2.1: no API, behavior, or dependency surface changes.
Changelog

Sourced from guardagent's changelog.

v3.2.3 (2026-10-12)

User-Agent identifies the TypeScript agent (v3.2.3)

Changed

  • The ingestion User-Agent header is now guard-agent-ts/<version> (was guardagent/<version>), so the Guard SaaS can tell the TypeScript agent apart from the other ports. Lockstep release with the agent family at 3.2.3.

v3.2.2 (2026-10-09)

Guard-Core org migration metadata release (v3.2.2)

About this release

  • A metadata-only release cut in lockstep with the sibling agents (all five agents at 3.2.2). The guardagent package ships no code changes: the npm package metadata (repository, bugs, homepage) and every repository link moved to the Guard-Core org. Shipped so the agents family moves in lockstep with the engines and the other agent implementations.

Compatibility

  • Drop-in over 3.2.1: no API, behavior, or dependency surface changes.
Commits
  • b854510 release(3.2.3): User-Agent guard-agent-ts, lockstep with the engines at 4.3.3...
  • d5cab4e chore(ci): relay development activity to the family Discord channel (#34)
  • fc58ebb docs(readme): content parity - corrected ecosystem tables, documentation and ...
  • f916b94 docs(readme): the guard-core legend, badges, and org links header (#30)
  • d6cd618 release(3.2.2): Guard-Core org migration metadata release (#29)
  • 922bbcf fix(demo): copy tsup.config.ts so the build finds its entry points (#28)
  • a597932 ci(container): publish the containerized agent demo to GHCR (#27)
  • d7a2d94 chore(deps-dev): bump the npm group across 1 directory with 3 updates (#25)
  • 44b4108 chore: repoint metadata to Guard-Core org (post-transfer sweep) (#26)
  • See full diff in compare view

Updates fastify-plugin from 6.0.0 to 6.0.1

Release notes

Sourced from fastify-plugin's releases.

v6.0.1

What's Changed

New Contributors

Full Changelog: fastify/fastify-plugin@v6.0.0...v6.0.1

Commits
  • 881fb92 Bumped v6.0.1
  • 9cd4e50 ci: enable trusted publishing releases
  • 7ba9af5 fix(lib/getpluginname): preserve hyphenated anonymous plugin names (#303)
  • 1471db6 fix(index): type check options.name (#308)
  • 56f07ad perf(index): skip camelCase for auto-named plugins (#307)
  • 9698476 fix(index): do not mutate options object (#305)
  • 2c28ce1 perf(lib/tocamelcase): hoist regex and replacer (#309)
  • af23fc7 style(lib/getpluginname): use upper snakecase for regex consts (#311)
  • 0c4f161 perf(index): hoist Symbol.for lookups to module-level
  • 8bb7751 test: run esm test once
  • Additional commits viewable in compare view
Maintainer changes

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


Updates @fastify/cors from 11.3.0 to 11.3.1

Release notes

Sourced from @​fastify/cors's releases.

v11.3.1

What's Changed

New Contributors

Full Changelog: fastify/fastify-cors@v11.3.0...v11.3.1

Commits
  • a4fb482 Bumped v11.3.1
  • 4627a17 ci: enable trusted publishing releases
  • 7670483 chore: bump fastify/workflows/.github/workflows/lock-threads.yml (#418)
  • d03ec98 chore: bump fastify/workflows/.github/workflows/plugins-ci.yml (#417)
  • 5a2e0d0 chore(.npmrc): add min-release-age
  • 2a47537 chore: return to typescript v6.x
  • 10c73be chore: bump typescript (#412)
  • b9f74b7 chore: bump c8 from 11.0.0 to 12.0.0 (#414)
  • 61789f1 ci: pin actions to commit-hash
  • See full diff in compare view
Maintainer changes

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


Updates hono from 4.13.11 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

v4.13.12

What's Changed

  • fix(build): keep internal types private in bundled d.ts and avoid a self-referencing JSX.IntrinsicElements in honojs/hono#5485
  • test(build): type-check the bundled declarations from a consumer project in honojs/hono#5486
  • fix(etag): correctly match mixed-case header name in retainedHeader option in honojs/hono#5475
  • fix(jsx): add px to numeric gridGap, gridRowGap and gridColumnGap in honojs/hono#5487
  • fix(combine): return a Response from a short-circuiting middleware in some() in honojs/hono#5391
  • chore(deps): upgrade vite-plus to 1.0.0 in honojs/hono#5464

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

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...
  • 6abd35b 4.13.12
  • 95eb860 chore(deps): upgrade vite-plus to 1.0.0 (#5464)
  • afb2068 fix(combine): return a Response from a short-circuiting middleware in some() ...
  • e5bb206 fix(jsx): add px to numeric gridGap, gridRowGap and gridColumnGap (#5487)
  • c3053cc fix(etag): correctly match mixed-case header name in retainedHeader option (#...
  • Additional commits viewable in compare view

Updates @nestjs/common from 12.1.1 to 12.1.3

Release notes

Sourced from @​nestjs/common's releases.

v12.1.3 (2026-10-12)

Bug fixes

... (truncated)

Commits
  • 4514623 chore(release): publish v12.1.3 release
  • c5b7187 fix(common): keep custom decorator data that has schema or pipes keys (#18090)
  • 406c402 fix(common): reject arrays nested in ParseArrayPipe items (#18073)
  • 5291521 fix(common,core,express): answer method miss on an excluded route (#17923)
  • ea340b1 fix(common): collect configurable module alias dependencies (#17999)
  • 1162fdc test(common): cover serializer context group overrides (#18026)
  • 5eb62e2 fix(common): isolate file type regexp state (#17983)
  • c318730 fix(common): preserve parent validation constraints (#17982)
  • a468f79 fix(common): let a redeclared @Inject() property replace the parent's (#17949)
  • 97c6e4f fix(common): keep inherited @Optional() properties optional (#17944)
  • Additional commits viewable in compare view

Updates @nestjs/core from 12.1.1 to 12.1.3

Release notes

Sourced from @​nestjs/core's releases.

v12.1.3 (2026-10-12)

Bug fixes

... (truncated)

Commits
  • 4514623 chore(release): publish v12.1.3 release
  • 77613d6 fix(core,microservices): flush buffered logs when initialization fails (#18111)
  • 2962bc2 fix(core): fail at startup for request-scoped class global enhancers (#18104)
  • 1da34ad fix(core): stop silently dropping request-scoped global enhancers (#18066)
  • b33a988 fix(core): resolve uri versioned exclusions for the not-found handler (#18072)
  • f1a4d30 fix(core): normalize slashes when mapping controllers for middleware (#18075)
  • 336a555 fix(core): do not mutate the message when assigning an sse event id (#18086)
  • f4b5ff4 fix(core): end sse streams whose event data cannot be serialized (#18025)
  • 5291521 fix(common,core,express): answer method miss on an excluded route (#17923)
  • d10b7c0 fix(core): send status and headers set by handlers on sse responses (#18011)
  • Additional commits viewable in compare view

Updates express from 4.22.3 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

🚀 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

🚀 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()) alon...

    Description has been truncated

Bumps the production group with 10 updates:

| Package | From | To |
| --- | --- | --- |
| [zod](https://github.com/colinhacks/zod) | `4.6.5` | `4.6.7` |
| [guardagent](https://github.com/Guard-Core/guard-agent-ts) | `3.2.1` | `3.2.3` |
| [fastify-plugin](https://github.com/fastify/fastify-plugin) | `6.0.0` | `6.0.1` |
| [@fastify/cors](https://github.com/fastify/fastify-cors) | `11.3.0` | `11.3.1` |
| [hono](https://github.com/honojs/hono) | `4.13.11` | `4.13.13` |
| [@nestjs/common](https://github.com/nestjs/nest/tree/HEAD/packages/common) | `12.1.1` | `12.1.3` |
| [@nestjs/core](https://github.com/nestjs/nest/tree/HEAD/packages/core) | `12.1.1` | `12.1.3` |
| [express](https://github.com/expressjs/express) | `4.22.3` | `5.3.0` |
| [@hono/node-server](https://github.com/honojs/node-server) | `2.1.3` | `2.1.4` |
| [@nestjs/platform-express](https://github.com/nestjs/nest/tree/HEAD/packages/platform-express) | `12.1.1` | `12.1.3` |


Updates `zod` from 4.6.5 to 4.6.7
- [Release notes](https://github.com/colinhacks/zod/releases)
- [Commits](colinhacks/zod@v4.6.5...v4.6.7)

Updates `guardagent` from 3.2.1 to 3.2.3
- [Release notes](https://github.com/Guard-Core/guard-agent-ts/releases)
- [Changelog](https://github.com/Guard-Core/guard-agent-ts/blob/master/CHANGELOG.md)
- [Commits](Guard-Core/guard-agent-ts@v3.2.1...v3.2.3)

Updates `fastify-plugin` from 6.0.0 to 6.0.1
- [Release notes](https://github.com/fastify/fastify-plugin/releases)
- [Commits](fastify/fastify-plugin@v6.0.0...v6.0.1)

Updates `@fastify/cors` from 11.3.0 to 11.3.1
- [Release notes](https://github.com/fastify/fastify-cors/releases)
- [Commits](fastify/fastify-cors@v11.3.0...v11.3.1)

Updates `hono` from 4.13.11 to 4.13.13
- [Release notes](https://github.com/honojs/hono/releases)
- [Commits](honojs/hono@v4.13.11...v4.13.13)

Updates `@nestjs/common` from 12.1.1 to 12.1.3
- [Release notes](https://github.com/nestjs/nest/releases)
- [Commits](https://github.com/nestjs/nest/commits/v12.1.3/packages/common)

Updates `@nestjs/core` from 12.1.1 to 12.1.3
- [Release notes](https://github.com/nestjs/nest/releases)
- [Commits](https://github.com/nestjs/nest/commits/v12.1.3/packages/core)

Updates `express` from 4.22.3 to 5.3.0
- [Release notes](https://github.com/expressjs/express/releases)
- [Changelog](https://github.com/expressjs/express/blob/master/History.md)
- [Commits](expressjs/express@v4.22.3...v5.3.0)

Updates `@hono/node-server` from 2.1.3 to 2.1.4
- [Release notes](https://github.com/honojs/node-server/releases)
- [Commits](honojs/node-server@v2.1.3...v2.1.4)

Updates `@nestjs/platform-express` from 12.1.1 to 12.1.3
- [Release notes](https://github.com/nestjs/nest/releases)
- [Commits](https://github.com/nestjs/nest/commits/v12.1.3/packages/platform-express)

---
updated-dependencies:
- dependency-name: zod
  dependency-version: 4.6.7
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production
- dependency-name: guardagent
  dependency-version: 3.2.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production
- dependency-name: fastify-plugin
  dependency-version: 6.0.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production
- dependency-name: "@fastify/cors"
  dependency-version: 11.3.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production
- dependency-name: hono
  dependency-version: 4.13.13
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production
- dependency-name: "@nestjs/common"
  dependency-version: 12.1.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production
- dependency-name: "@nestjs/core"
  dependency-version: 12.1.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production
- dependency-name: express
  dependency-version: 5.3.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: production
- dependency-name: "@hono/node-server"
  dependency-version: 2.1.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production
- dependency-name: "@nestjs/platform-express"
  dependency-version: 12.1.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot requested a review from rennf93 as a code owner October 16, 2026 06:25
@dependabot dependabot Bot added dependencies package.json or pnpm-lock.yaml javascript Pull requests that update javascript code labels Oct 16, 2026
@github-actions

Copy link
Copy Markdown

Thanks for opening your first pull request on guard-core-ts!

Quick checklist before review (most of these are enforced by CI, but worth a glance):

  • pnpm install — workspace resolves cleanly
  • pnpm lint (or make lint) — turbo lint pipeline passes for every package you touched
  • pnpm test (or make test-all) — vitest suites pass across all packages
  • pnpm build — every package builds via tsup without warnings
  • Coverage didn't regress — make test-coverage
  • No // @ts-ignore / // @ts-expect-error / any shortcuts; pre-existing violations in touched files are fixed
  • Added an entry under ## Unreleased in CHANGELOG.md
  • If you touched a public API, updated the relevant page under docs/

See CONTRIBUTING.md for the full workflow and the Code of Conduct for the community standards we follow.

Welcome aboard — a maintainer will review shortly.

@github-actions github-actions Bot added package: express Changes inside @guardcore/express package: fastify Changes inside @guardcore/fastify package: hono Changes inside @guardcore/hono package: nestjs Changes inside @guardcore/nestjs examples examples/ apps labels Oct 16, 2026
@dependabot @github

dependabot Bot commented on behalf of github Oct 16, 2026

Copy link
Copy Markdown
Contributor Author

Looks like these dependencies are updatable in another way, so this is no longer needed.

@dependabot dependabot Bot closed this Oct 16, 2026
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/production-2169032fb0 branch October 16, 2026 10:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies package.json or pnpm-lock.yaml examples examples/ apps javascript Pull requests that update javascript code package: express Changes inside @guardcore/express package: fastify Changes inside @guardcore/fastify package: hono Changes inside @guardcore/hono package: nestjs Changes inside @guardcore/nestjs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants