Skip to content

chore(deps): bump the production-dependencies group across 1 directory with 4 updates - #70

Closed
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/production-dependencies-9576f2dafd
Closed

dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/production-dependencies-9576f2dafd

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 7, 2026

Copy link
Copy Markdown
Contributor

Bumps the production-dependencies group with 4 updates in the / directory: @fozikio/reflex, @modelcontextprotocol/sdk, better-sqlite3 and yaml.

Updates @fozikio/reflex from 0.2.0 to 0.2.1

Commits
Maintainer changes

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


Updates @modelcontextprotocol/sdk from 1.29.0 to 1.30.0

Release notes

Sourced from @​modelcontextprotocol/sdk's releases.

1.30.0

What's Changed

New Contributors

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

Commits
  • 2d889f2 chore: bump version to 1.30.0 (#2563)
  • e3f3daa Fix SSE keep-alive timer lifecycle in Streamable HTTP server transport (v1.x)...
  • bb5a718 fix(deps): widen @​hono/node-server past GHSA-frvp-7c67-39w9 (#2549)
  • 1dad263 fix: send SSE keep-alive comment frames from Streamable HTTP server transport...
  • 69749aa Validate Content-Type by parsed media type instead of substring match (v1.x) ...
  • 369513d fix: support Zod 3.25 method literals (#2368)
  • e7ee57c v1 stdio buffer limit (#2239)
  • c36e1ef Add end-to-end test suite (#2167)
  • bf1e022 chore(ci): switch publish to OIDC trusted publishing (#1839)
  • 9edbab7 fix(server): prioritize zod issues and format them (#1503)
  • See full diff in compare view
Maintainer changes

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


Updates better-sqlite3 from 11.10.0 to 13.0.3

Release notes

Sourced from better-sqlite3's releases.

v13.0.3

What's Changed

Full Changelog: WiseLibs/better-sqlite3@v13.0.2...v13.0.3

v13.0.2

What's Changed

New Contributors

Full Changelog: WiseLibs/better-sqlite3@v13.0.1...v13.0.2

v13.0.1

Full Changelog: WiseLibs/better-sqlite3@v13.0.0...v13.0.1

Fixed a regression in parameter binding where it would be overly strict and reject plain objects from other realms (e.g., in jest tests).

v13.0.0

Version 13.0.0 marks a major milestone, as it's the first version of better-sqlite3 to run on the N-API. This means prebuilt binaries should theoretically work across different versions of Node.js and Electron, and perhaps even other runtimes like Bun. As a result, we've removed the deprecated prebuild-install dependency, and now prebuilt binaries are published directly with the better-sqlite3 code itself. If your platform/architecture doesn't have a prebuilt binary, it should compile during install as before.

What's Changed

New Contributors

Full Changelog: WiseLibs/better-sqlite3@v12.12.0...v13.0.0

v12.12.0

What's Changed

[!WARNING]

BREAKING: Starting with Electron v43, binary assets will require glibc 2.41 or higher on Linux hosts.

... (truncated)

Commits
Maintainer changes

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


Updates yaml from 2.8.3 to 2.9.0

Release notes

Sourced from yaml's releases.

v2.9.0

The changes here are really only patches, but I'm releasing this as a minor version to note a small change to the documentation of parseDocument() and parseAllDocuments(): I've removed the claim that they'll "never throw".

It remains the case that practically all non-malicious inputs will be handled without emitting an error, but there is a decent chance that code paths remain where e.g. a RangeError due to call stack exhaustion can be triggered by malicious inputs. Up to now, I've considered these as security vulnerabilities, and in fact it's the only category of error for which yaml CVEs have been issued so far.

Starting from this release, I'll be considering such errors as bugs, but not vulnerabilities. I do welcome people and/or LLMs looking for them, but please report them as normal issues rather than suspected security vulnerabilities. This also applies to previously undiscovered bugs in earlier releases.

  • fix: Avoid calling Array.prototype.push.apply() with large source array
  • fix(lexer): Avoid recursive calls that may exhaust the call stack

v2.8.4

  • Disable alias resolution with maxAliasCount:0 (#677)
  • Handle invalid unicode escapes (e1a1a77)
  • Apply minFractionDigits only to decimal strings (#676)
Commits
  • ddb21b0 2.9.0
  • 167365b docs: Clarify that not all errors can be avoided
  • 6eca2a7 fix: Avoid calling Array.prototype.push.apply() with large source array
  • 0543cd5 fix(lexer): Avoid recursive calls that may exhaust the call stack
  • ccdf743 2.8.4
  • f625789 fix: Disable alias resolution with maxAliasCount:0 (#677)
  • e1a1a77 fix: Handle invalid unicode escapes
  • a163ea0 style: Satify Prettier
  • b2a5a6c fix: Apply minFractionDigits only to decimal strings (#676)
  • 93c951b chore: Bump JSR version to v2.8.3 (#673)
  • 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 Sep 7, 2026
@dependabot
dependabot Bot requested a review from idapixl as a code owner September 7, 2026 21:26
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Sep 7, 2026
@dependabot dependabot Bot changed the title chore(deps): bump the production-dependencies group with 4 updates chore(deps): bump the production-dependencies group across 1 directory with 4 updates Sep 7, 2026
…y with 4 updates

Bumps the production-dependencies group with 4 updates in the / directory: [@fozikio/reflex](https://github.com/Fozikio/reflex), [@modelcontextprotocol/sdk](https://github.com/modelcontextprotocol/typescript-sdk), [better-sqlite3](https://github.com/WiseLibs/better-sqlite3) and [yaml](https://github.com/eemeli/yaml).


Updates `@fozikio/reflex` from 0.2.0 to 0.2.1
- [Commits](https://github.com/Fozikio/reflex/commits/v0.2.1)

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

Updates `better-sqlite3` from 11.10.0 to 13.0.3
- [Release notes](https://github.com/WiseLibs/better-sqlite3/releases)
- [Commits](WiseLibs/better-sqlite3@v11.10.0...v13.0.3)

Updates `yaml` from 2.8.3 to 2.9.0
- [Release notes](https://github.com/eemeli/yaml/releases)
- [Commits](eemeli/yaml@v2.8.3...v2.9.0)

---
updated-dependencies:
- dependency-name: "@fozikio/reflex"
  dependency-version: 0.2.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-dependencies
- dependency-name: "@modelcontextprotocol/sdk"
  dependency-version: 1.30.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-dependencies
- dependency-name: better-sqlite3
  dependency-version: 13.0.3
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: production-dependencies
- dependency-name: yaml
  dependency-version: 2.9.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/production-dependencies-9576f2dafd branch from 944fb47 to bef79cd Compare September 7, 2026 21:35
@idapixl

idapixl commented Sep 10, 2026

Copy link
Copy Markdown
Collaborator

Holding this one, with a reason rather than a rebase loop.

The Node 20 Compat failure is the gate working, not a flake. This bumps better-sqlite3 11 → 13, and 13 declares "engines": { "node": ">=22" } while cortex-engine declares >=20. Merging as-is would drop Node 20 support for every installer without a version bump saying so — the failing job is the only thing currently preventing that.

The other three updates in this group are fine. It's specifically the better-sqlite3 major that forces the choice.

That choice is real and probably due soon: Node 20 reached end-of-life on 2026-04-30, and the CI logs already warn that checkout@v4/setup-node@v4 are being forced onto Node 24. Dropping Node 20 is defensible — but it's a breaking change for consumers and belongs in a deliberate release with engines raised to >=22 in the same commit, not in a dependency-group merge.

Leaving open for that decision. Not a security hold: npm install @fozikio/cortex-engine currently reports 0 vulnerabilities.

@dependabot @github

dependabot Bot commented on behalf of github Sep 10, 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 Sep 10, 2026
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/production-dependencies-9576f2dafd branch September 10, 2026 16:40
idapixl added a commit that referenced this pull request Sep 13, 2026
…0) (#79)

* feat(engines)!: require Node 22; better-sqlite3 13 and vitest 5

Node 20 reached end-of-life on 2026-04-30. The reason to move now is
mechanical rather than hygienic: better-sqlite3 13 declares node>=22,
and vitest 5 cannot run against better-sqlite3 11 — its worker
lifecycle tears the addon down on a null N-API env (SIGABRT, Linux
runner only). Dependabot #70 and #72 had each been failing on one half
of that coupling for a week. Taking both in one deliberate release,
with the engines change called out first in the changelog, instead of
letting a dependency-group merge drop Node 20 silently.

The Node 20 Compat CI job becomes Node 22 Compat — same purpose, one
floor higher. Also cuts the 1.4.2 changelog heading that the 09-10
release shipped without.

Closes #76. Supersedes #70, #72, #74, #77.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

* fix(doctor): enforce the Node 22 floor everywhere the old one was stated

Review caught three places still saying Node 20: the doctor runtime
check (which would have reported a Node 20 install healthy while
better-sqlite3 13 cannot build there), CONTRIBUTING's setup text, and
the changelog's claim that npm "refuses" a Node 20 install — it only
warns unless engine-strict is set; the refusal comes from the native
build.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
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