Skip to content

chore(deps): bump the npm-minor-patch group across 1 directory with 6 updates - #1036

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/vmark-mcp-server/npm-minor-patch-6217382fda
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/vmark-mcp-server/npm-minor-patch-6217382fda

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 16, 2026

Copy link
Copy Markdown
Contributor

Bumps the npm-minor-patch group with 6 updates in the /vmark-mcp-server directory:

Package From To
@modelcontextprotocol/sdk 1.27.1 1.29.0
ws 8.18.3 8.21.0
@vitest/coverage-v8 4.0.16 4.1.9
@yao-pkg/pkg 6.14.1 6.20.0
esbuild 0.27.2 0.28.1
vitest 4.0.16 4.1.9

Updates @modelcontextprotocol/sdk from 1.27.1 to 1.29.0

Release notes

Sourced from @​modelcontextprotocol/sdk's releases.

v1.29.0

What's Changed

New Contributors

Full Changelog: modelcontextprotocol/typescript-sdk@v1.28.0...v1.29.0

v1.28.0

What's Changed

New Contributors

Full Changelog: modelcontextprotocol/typescript-sdk@v1.27.1...v1.28.0

Commits

Updates ws from 8.18.3 to 8.21.0

Release notes

Sourced from ws's releases.

8.21.0

Features

  • Introduced the maxBufferedChunks and maxFragments options (2b2abd45).

Bug fixes

  • Fixed a remote memory exhaustion DoS vulnerability (2b2abd45).

A high volume of tiny fragments and data chunks could be sent by a peer, using modest network traffic, to crash a ws server or client due to OOM.

import { WebSocket, WebSocketServer } from 'ws';
const wss = new WebSocketServer({ port: 0 }, function () {
const data = Buffer.alloc(1);
const options = { fin: false };
const { port } = wss.address();
const ws = new WebSocket(ws://localhost:${port});
ws.on('open', function () {
(function send() {
ws.send(data, options, function (err) {
if (err) return;
send();
});
})();
});
ws.on('error', console.error);
ws.on('close', function (code, reason) {
console.log(client close - code: ${code} reason: ${reason.toString()});
});
});
wss.on('connection', function (ws) {
ws.on('error', console.error);
ws.on('close', function (code, reason) {
console.log(server close - code: ${code} reason: ${reason.toString()});
});
});

The vulnerability was responsibly disclosed and fixed by Nadav Magier.

In vulnerable versions, the issue can be mitigated by lowering the value of the maxPayload option if possible.

8.20.1

... (truncated)

Commits
  • bca91ad [dist] 8.21.0
  • 2b2abd4 [security] Limit retained message parts
  • 78eabe2 [security] Add latest vulnerability to SECURITY.md
  • 5d9b316 [dist] 8.20.1
  • c0327ec [security] Fix uninitialized memory disclosure in websocket.close()
  • ce2a3d6 [ci] Test on node 26
  • 58e45b8 [ci] Do not test on node 25
  • 5f26c24 [ci] Run the lint step on node 24
  • 8439255 [dist] 8.20.0
  • d3503c1 [minor] Export the PerMessageDeflate class and header utils
  • Additional commits viewable in compare view

Updates @vitest/coverage-v8 from 4.0.16 to 4.1.9

Release notes

Sourced from @​vitest/coverage-v8's releases.

v4.1.9

🐞 Bug Fixes

View changes on GitHub

v4.1.8

   🐞 Bug Fixes

    View changes on GitHub

v4.1.7

   🐞 Bug Fixes

    View changes on GitHub

v4.1.6

   🐞 Bug Fixes

   🏎 Performance

    View changes on GitHub

v4.1.5

   🚀 Experimental Features

   🐞 Bug Fixes

... (truncated)

Commits

Updates @yao-pkg/pkg from 6.14.1 to 6.20.0

Release notes

Sourced from @​yao-pkg/pkg's releases.

Release 6.19.0

6.19.0 (2026-04-24)

Features

  • config: accept CLI-only build flags in pkg config (#263) (a8e91df)

Bug Fixes

  • deps: update @​roberts_lando/vfs to version 0.3.3 (#266) (d155e24)
  • detector: stop silent dependency drops in SEA mode (ESM parse, dynamic import, decorators) (#268) (81c6c88)
  • sea: silence benign LIEF warnings during postject injection (#265) (974df53)

Release 6.18.2

6.18.2 (2026-04-22)

Bug Fixes

  • sea: match blob generator to target Node version (#247) (ad2a336), closes #236
  • sea: strip trailing slashes in manifest key lookup (#261) (af0c086)

Release 6.18.1

6.18.1 (2026-04-21)

Bug Fixes

  • pkg: ship all .d.ts files in npm package (#258) (7e10ce2)

Release 6.18.0

6.18.0 (2026-04-20)

Features

Documentation

  • tighten guide pages — remove AI-slop headings and verbose framing (cc331fa)

Release 6.17.0

6.17.0 (2026-04-18)

Features

  • sea: add per-file compression to SEA archive (closes #250) (#251) (fdf8046)

Documentation

  • add in-depth comparison vs Bun and Deno (#249) (0cf75a8)

... (truncated)

Changelog

Sourced from @​yao-pkg/pkg's changelog.

Changelog

6.19.0 (2026-04-24)

Features

  • config: accept CLI-only build flags in pkg config (#263) (a8e91df)

Bug Fixes

  • deps: update @​roberts_lando/vfs to version 0.3.3 (#266) (d155e24)
  • detector: stop silent dependency drops in SEA mode (ESM parse, dynamic import, decorators) (#268) (81c6c88)
  • sea: silence benign LIEF warnings during postject injection (#265) (974df53)

6.18.2 (2026-04-22)

Bug Fixes

6.18.1 (2026-04-21)

Bug Fixes

  • pkg: ship all .d.ts files in npm package (#258) (7e10ce2)

6.18.0 (2026-04-20)

Features

Documentation

  • tighten guide pages — remove AI-slop headings and verbose framing (cc331fa)

6.17.0 (2026-04-18)

Features

  • sea: add per-file compression to SEA archive (closes #250) (#251) (fdf8046)

Documentation

  • add in-depth comparison vs Bun and Deno (#249) (0cf75a8)

6.16.0 (2026-04-17)

... (truncated)

Commits
Maintainer changes

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


Updates esbuild from 0.27.2 to 0.28.1

Release notes

Sourced from esbuild's releases.

v0.28.1

  • Disallow \ in local development server HTTP requests (GHSA-g7r4-m6w7-qqqr)

    This release fixes a security issue where HTTP requests to esbuild's local development server could traverse outside of the serve directory on Windows using a \ backslash character. It happened due to the use of Go's path.Clean() function, which only handles Unix-style / characters. HTTP requests with paths containing \ are no longer allowed.

    Thanks to @​dellalibera for reporting this issue.

  • Add integrity checks to the Deno API (GHSA-gv7w-rqvm-qjhr)

    The previous release of esbuild added integrity checks to esbuild's npm install script. This release also adds integrity checks to esbuild's Deno install script. Now esbuild's Deno API will also fail with an error if the downloaded esbuild binary contains something other than the expected content.

    Note that esbuild's Deno API installs from registry.npmjs.org by default, but allows the NPM_CONFIG_REGISTRY environment variable to override this with a custom package registry. This change means that the esbuild executable served by NPM_CONFIG_REGISTRY must now match the expected content.

    Thanks to @​sondt99 for reporting this issue.

  • Avoid inlining using and await using declarations (#4482)

    Previously esbuild's minifier sometimes incorrectly inlined using and await using declarations into subsequent uses of that declaration, which then fails to dispose of the resource correctly. This bug happened because inlining was done for let and const declarations by avoiding doing it for var declarations, which no longer worked when more declaration types were added. Here's an example:

    // Original code
    {
      using x = new Resource()
      x.activate()
    }
    // Old output (with --minify)
    new Resource().activate();
    // New output (with --minify)
    {using e=new Resource;e.activate()}

  • Fix module evaluation when an error is thrown (#4461, #4467)

    If an error is thrown during module evaluation, esbuild previously didn't preserve the state of the module for subsequent module references. This was observable if import() or require() is used to import a module multiple times. The thrown error is supposed to be thrown by every call to import() or require(), not just the first. With this release, esbuild will now throw the same error every time you call import() or require() on a module that throws during its evaluation.

  • Fix some edge cases around the new operator (#4477)

    Previously esbuild incorrectly printed certain edge cases involving complex expressions inside the target of a new expression (specifically an optional chain and/or a tagged template literal). The generated code for the new target was not correctly wrapped with parentheses, and either contained a syntax error or had different semantics. These edge cases have been fixed so that they now correctly wrap the new target in parentheses. Here is an example of some affected code:

    // Original code
    new (foo()`bar`)()
    new (foo()?.bar)()
    // Old output
    new foo()bar();
    new (foo())?.bar();

... (truncated)

Changelog

Sourced from esbuild's changelog.

Changelog: 2025

This changelog documents all esbuild versions published in the year 2025 (versions 0.25.0 through 0.27.2).

Commits

Updates vitest from 4.0.16 to 4.1.9

Release notes

Sourced from vitest's releases.

v4.1.9

🐞 Bug Fixes

View changes on GitHub

v4.1.8

   🐞 Bug Fixes

    View changes on GitHub

v4.1.7

   🐞 Bug Fixes

    View changes on GitHub

v4.1.6

   🐞 Bug Fixes

   🏎 Performance

    View changes on GitHub

v4.1.5

   🚀 Experimental Features

   🐞 Bug Fixes

... (truncated)

Commits
  • a7a61e7 chore: release v4.1.9 (#10598)
  • 934b0f5 fix(pool): prevent test run hang on worker crash (#10543) [backport to v4] (#...
  • 7fb2965 fix(browser): wait for orchestrator readiness before resolving browser sessio...
  • a518019 fix: fix importOriginal with optimizer and query import [backport to v4] (#...
  • e61f2dd chore: release v4.1.8
  • e4067b3 fix(browser): disable client cdp API when allowWrite/allowExec: false [ba...
  • a09d472 chore: release v4.1.7
  • a8fd24c chore: release v4.1.6
  • 18af98c fix(browser): simplify orchestrator otel carrier (#10285)
  • 3188260 feat(browser): provide project reference in ToMatchScreenshotResolvePath (#...
  • Additional commits viewable in compare view

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Jun 16, 2026
@xiaolai
xiaolai enabled auto-merge (squash) June 27, 2026 01:16
@xiaolai

xiaolai commented Jun 27, 2026

Copy link
Copy Markdown
Owner

@dependabot recreate

… updates

Bumps the npm-minor-patch group with 6 updates in the /vmark-mcp-server directory:

| Package | From | To |
| --- | --- | --- |
| [@modelcontextprotocol/sdk](https://github.com/modelcontextprotocol/typescript-sdk) | `1.27.1` | `1.29.0` |
| [ws](https://github.com/websockets/ws) | `8.18.3` | `8.21.0` |
| [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) | `4.0.16` | `4.1.9` |
| [@yao-pkg/pkg](https://github.com/yao-pkg/pkg) | `6.14.1` | `6.20.0` |
| [esbuild](https://github.com/evanw/esbuild) | `0.27.2` | `0.28.1` |
| [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) | `4.0.16` | `4.1.9` |



Updates `@modelcontextprotocol/sdk` from 1.27.1 to 1.29.0
- [Release notes](https://github.com/modelcontextprotocol/typescript-sdk/releases)
- [Commits](modelcontextprotocol/typescript-sdk@v1.27.1...v1.29.0)

Updates `ws` from 8.18.3 to 8.21.0
- [Release notes](https://github.com/websockets/ws/releases)
- [Commits](websockets/ws@8.18.3...8.21.0)

Updates `@vitest/coverage-v8` from 4.0.16 to 4.1.9
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md)
- [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.9/packages/coverage-v8)

Updates `@yao-pkg/pkg` from 6.14.1 to 6.20.0
- [Release notes](https://github.com/yao-pkg/pkg/releases)
- [Changelog](https://github.com/yao-pkg/pkg/blob/main/CHANGELOG.md)
- [Commits](https://github.com/yao-pkg/pkg/commits)

Updates `esbuild` from 0.27.2 to 0.28.1
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG-2025.md)
- [Commits](evanw/esbuild@v0.27.2...v0.28.1)

Updates `vitest` from 4.0.16 to 4.1.9
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md)
- [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.9/packages/vitest)

---
updated-dependencies:
- dependency-name: "@modelcontextprotocol/sdk"
  dependency-version: 1.29.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm-minor-patch
- dependency-name: "@vitest/coverage-v8"
  dependency-version: 4.1.9
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-minor-patch
- dependency-name: "@yao-pkg/pkg"
  dependency-version: 6.20.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-minor-patch
- dependency-name: esbuild
  dependency-version: 0.28.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-minor-patch
- dependency-name: vitest
  dependency-version: 4.1.9
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-minor-patch
- dependency-name: ws
  dependency-version: 8.21.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm-minor-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title chore(deps): bump the npm-minor-patch group in /vmark-mcp-server with 6 updates chore(deps): bump the npm-minor-patch group across 1 directory with 6 updates Jun 27, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/vmark-mcp-server/npm-minor-patch-6217382fda branch from 055b4ed to e46bdd8 Compare June 27, 2026 01:21
xiaolai added a commit that referenced this pull request Jun 27, 2026
`pnpm update -r` within semver — reproduces the dependabot minor/patch groups
#1045 (root), #1036 (mcp), and #1051 (@eslint/js) as one verified change.
Full `pnpm check:all` green.

- Size growth accepted (approved): mermaid 11.12 → 11.16 (+~800 kB, lazy
  chunk — never in cold start) and tiptap 3.18 → 3.27 (+18 kB eager). Both
  size-limit ceilings bumped with documented reasons in .size-limit.cjs.
- schema.ts: vscode-languageserver-types reached LSP 3.18, which widened
  Diagnostic.message to `string | MarkupContent`; flatten MarkupContent to
  its text via a messageText() helper.

Completes #1045 / #1036 / #1051.
@xiaolai

xiaolai commented Jun 27, 2026

Copy link
Copy Markdown
Owner

Superseded by #1062 — folded into the consolidated dependency PR (minor/patch sweep, verified green). Size growth from mermaid/tiptap accepted with documented size-limit bumps.

@xiaolai xiaolai closed this Jun 27, 2026
auto-merge was automatically disabled June 27, 2026 03:08

Pull request was closed

@dependabot @github

dependabot Bot commented on behalf of github Jun 27, 2026

Copy link
Copy Markdown
Contributor Author

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml

@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/vmark-mcp-server/npm-minor-patch-6217382fda branch June 27, 2026 03:08
xiaolai added a commit that referenced this pull request Jun 27, 2026
…h, done correctly) (#1062)

* chore(deps): upgrade rust-i18n 3→4, dirs 5→6, toml 0.8→0.9

All three are drop-in for VMark's usage — verified locally with
`cargo check` + 728 passing tests:

- rust-i18n 4: the 3→4 breaking changes are all trait-level (custom Backend
  impls + the dropped once_cell re-export). We use only the i18n!/t! macros
  and set_locale, which are unchanged. MSRV 1.80 is satisfied.
- dirs 6: home_dir() is unchanged (our only call); we never use config_dir,
  so its macOS churn is irrelevant.
- toml 0.9: we parse into toml::Table (not Value, sidestepping the
  FromStr-now-parses-values break) and use to_string_pretty (signature
  unchanged). Resolves to 0.9.10 — the +spec-1.1.0 suffix is build metadata
  on the published 0.9.10, not a separate preview track.

Completes the intent of dependabot #1044 / #1042 / #1043, which failed as
blind bumps, done correctly with verification.

* chore(deps): upgrade JS majors — i18next 26, lucide-react 1, zod 4 (mcp), react-i18next 16.6

Done correctly with the code migrations dependabot's blind bumps couldn't do.
Verified with the full `pnpm check:all` (tsc, lint, sidecar + content-server
tests, build, coverage, size).

- i18next 25 → 26: `initImmediate` was removed; renamed back to `initAsync`
  (same semantics). src/i18n.ts updated. react-i18next bumped 16.5 → 16.6
  (peer `>= 25.10.9` admits i18next 26).
- lucide-react 0.562 → 1.x: v1 removed all brand icons. AboutSettings imported
  the now-removed `Github`, so it ships the GitHub mark as a local inline SVG
  (GithubMark.tsx) matching the lucide render contract. All other 74 icons
  resolve unchanged. Settings-page size limit nudged 94 → 95 kB for the SVG.
- zod 3 → 4 (vmark-mcp-server): single-arg `z.record()` was removed; cli.ts now
  passes an explicit key schema (`z.record(z.string(), z.unknown())`). The MCP
  SDK 1.27.1 peers `^3.25 || ^4.0`, so zod 4 is accepted.

Completes the intent of dependabot #1052 / #1046 / #1037 / #1047.

* chore(deps): dev-tooling majors (vite-plugin-react 5, react-hooks 7, globals 17) + cargo minor/patch group

Verified with full `pnpm check:all` (lint, build, coverage, sidecar,
content-server, size) + `cargo check` + 728 Rust tests.

- @vitejs/plugin-react 4 → 5, globals 16 → 17: drop-in (dev/build only, no
  bundle impact). Replaces #1048, #1054.
- eslint-plugin-react-hooks 5 → 7: v7 folded the React Compiler rule set into
  `recommended`, flagging 67 pre-existing sites (set-state-in-effect, refs,
  manual-memoization, immutability). Adopting those is a deliberate codebase
  refactor, not a version bump — so they're deferred in eslint.config.js
  (documented) to preserve the prior enforcement level, and exhaustive-deps is
  pinned to its historical `warn`. Replaces #1050.
- cargo minor/patch updates within semver (`cargo update`): reproduces the
  cargo-minor-patch group (#1040), which failed as a blind bump against a
  stale base. Compiles clean + all Rust tests pass.

Note: the root npm minor/patch group (#1045) is intentionally NOT swept in
here — it carries a mermaid 11.12→11.16 (+~800 kB lazy chunk) and tiptap
3.18→3.27 growth that trips the size gate and warrants a separate, conscious
decision rather than an automatic limit bump. Left to dependabot.

* chore(deps): npm minor/patch sweep (root + mcp + content-server)

`pnpm update -r` within semver — reproduces the dependabot minor/patch groups
#1045 (root), #1036 (mcp), and #1051 (@eslint/js) as one verified change.
Full `pnpm check:all` green.

- Size growth accepted (approved): mermaid 11.12 → 11.16 (+~800 kB, lazy
  chunk — never in cold start) and tiptap 3.18 → 3.27 (+18 kB eager). Both
  size-limit ceilings bumped with documented reasons in .size-limit.cjs.
- schema.ts: vscode-languageserver-types reached LSP 3.18, which widened
  Diagnostic.message to `string | MarkupContent`; flatten MarkupContent to
  its text via a messageText() helper.

Completes #1045 / #1036 / #1051.

* docs(eslint): link react-hooks-7 rule deferral to tracking issue #1063

* fix(deps): reconcile pnpm-lock with dompurify override so --frozen-lockfile passes

The minor/patch sweep left pnpm-lock.yaml frozen-inconsistent: the direct
dompurify dep (^3.4.11) and the pnpm.overrides entry (>=3.3.2) disagreed in a
way non-frozen install tolerates but CI's --frozen-lockfile rejects
(ERR_PNPM_OUTDATED_LOCKFILE). Plain pnpm install reconciles it. check:all green.

* fix(knip): re-add mermaid + vitepress to website ignore lists

The minor/patch sweep shifted node_modules hoisting enough that knip (on a
clean --frozen-lockfile install, as CI runs) can no longer statically trace
the website's mermaid usage (rendered via vitepress's component system) or
resolve the `vitepress` binary — flagging both as error-level (Unused
devDependencies / Unlisted binaries). Both are genuinely used; the earlier
gate-fix removed these ignore entries as "stale," but they're load-bearing
across hoisting states. Verified with a clean install + full check:all.
xiaolai added a commit that referenced this pull request Aug 12, 2026
…h, done correctly) (#1062)

* chore(deps): upgrade rust-i18n 3→4, dirs 5→6, toml 0.8→0.9

All three are drop-in for VMark's usage — verified locally with
`cargo check` + 728 passing tests:

- rust-i18n 4: the 3→4 breaking changes are all trait-level (custom Backend
  impls + the dropped once_cell re-export). We use only the i18n!/t! macros
  and set_locale, which are unchanged. MSRV 1.80 is satisfied.
- dirs 6: home_dir() is unchanged (our only call); we never use config_dir,
  so its macOS churn is irrelevant.
- toml 0.9: we parse into toml::Table (not Value, sidestepping the
  FromStr-now-parses-values break) and use to_string_pretty (signature
  unchanged). Resolves to 0.9.10 — the +spec-1.1.0 suffix is build metadata
  on the published 0.9.10, not a separate preview track.

Completes the intent of dependabot #1044 / #1042 / #1043, which failed as
blind bumps, done correctly with verification.

* chore(deps): upgrade JS majors — i18next 26, lucide-react 1, zod 4 (mcp), react-i18next 16.6

Done correctly with the code migrations dependabot's blind bumps couldn't do.
Verified with the full `pnpm check:all` (tsc, lint, sidecar + content-server
tests, build, coverage, size).

- i18next 25 → 26: `initImmediate` was removed; renamed back to `initAsync`
  (same semantics). src/i18n.ts updated. react-i18next bumped 16.5 → 16.6
  (peer `>= 25.10.9` admits i18next 26).
- lucide-react 0.562 → 1.x: v1 removed all brand icons. AboutSettings imported
  the now-removed `Github`, so it ships the GitHub mark as a local inline SVG
  (GithubMark.tsx) matching the lucide render contract. All other 74 icons
  resolve unchanged. Settings-page size limit nudged 94 → 95 kB for the SVG.
- zod 3 → 4 (vmark-mcp-server): single-arg `z.record()` was removed; cli.ts now
  passes an explicit key schema (`z.record(z.string(), z.unknown())`). The MCP
  SDK 1.27.1 peers `^3.25 || ^4.0`, so zod 4 is accepted.

Completes the intent of dependabot #1052 / #1046 / #1037 / #1047.

* chore(deps): dev-tooling majors (vite-plugin-react 5, react-hooks 7, globals 17) + cargo minor/patch group

Verified with full `pnpm check:all` (lint, build, coverage, sidecar,
content-server, size) + `cargo check` + 728 Rust tests.

- @vitejs/plugin-react 4 → 5, globals 16 → 17: drop-in (dev/build only, no
  bundle impact). Replaces #1048, #1054.
- eslint-plugin-react-hooks 5 → 7: v7 folded the React Compiler rule set into
  `recommended`, flagging 67 pre-existing sites (set-state-in-effect, refs,
  manual-memoization, immutability). Adopting those is a deliberate codebase
  refactor, not a version bump — so they're deferred in eslint.config.js
  (documented) to preserve the prior enforcement level, and exhaustive-deps is
  pinned to its historical `warn`. Replaces #1050.
- cargo minor/patch updates within semver (`cargo update`): reproduces the
  cargo-minor-patch group (#1040), which failed as a blind bump against a
  stale base. Compiles clean + all Rust tests pass.

Note: the root npm minor/patch group (#1045) is intentionally NOT swept in
here — it carries a mermaid 11.12→11.16 (+~800 kB lazy chunk) and tiptap
3.18→3.27 growth that trips the size gate and warrants a separate, conscious
decision rather than an automatic limit bump. Left to dependabot.

* chore(deps): npm minor/patch sweep (root + mcp + content-server)

`pnpm update -r` within semver — reproduces the dependabot minor/patch groups
#1045 (root), #1036 (mcp), and #1051 (@eslint/js) as one verified change.
Full `pnpm check:all` green.

- Size growth accepted (approved): mermaid 11.12 → 11.16 (+~800 kB, lazy
  chunk — never in cold start) and tiptap 3.18 → 3.27 (+18 kB eager). Both
  size-limit ceilings bumped with documented reasons in .size-limit.cjs.
- schema.ts: vscode-languageserver-types reached LSP 3.18, which widened
  Diagnostic.message to `string | MarkupContent`; flatten MarkupContent to
  its text via a messageText() helper.

Completes #1045 / #1036 / #1051.

* docs(eslint): link react-hooks-7 rule deferral to tracking issue #1063

* fix(deps): reconcile pnpm-lock with dompurify override so --frozen-lockfile passes

The minor/patch sweep left pnpm-lock.yaml frozen-inconsistent: the direct
dompurify dep (^3.4.11) and the pnpm.overrides entry (>=3.3.2) disagreed in a
way non-frozen install tolerates but CI's --frozen-lockfile rejects
(ERR_PNPM_OUTDATED_LOCKFILE). Plain pnpm install reconciles it. check:all green.

* fix(knip): re-add mermaid + vitepress to website ignore lists

The minor/patch sweep shifted node_modules hoisting enough that knip (on a
clean --frozen-lockfile install, as CI runs) can no longer statically trace
the website's mermaid usage (rendered via vitepress's component system) or
resolve the `vitepress` binary — flagging both as error-level (Unused
devDependencies / Unlisted binaries). Both are genuinely used; the earlier
gate-fix removed these ignore entries as "stale," but they're load-bearing
across hoisting states. Verified with a clean install + full check:all.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant