Skip to content

fix(deps): update all non-major dependencies - #2515

Draft
renovate[bot] wants to merge 5 commits into
mainfrom
renovate/all-minor-patch
Draft

renovate[bot] wants to merge 5 commits into
mainfrom
renovate/all-minor-patch

Conversation

@renovate

@renovate renovate Bot commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Type Update Pending
@aws-sdk/client-s3 (source) 3.1116.03.1123.0 age confidence dependencies minor 3.1127.0 (+3)
@aws-sdk/lib-storage (source) 3.1116.03.1123.0 age confidence dependencies minor 3.1127.0 (+3)
@harperfast/skills (source) 1.12.21.12.5 age confidence dependencies patch 1.12.8 (+2)
@typescript-eslint/parser (source) 8.67.08.69.0 age confidence devDependencies minor 8.70.0
axios (source) 1.19.01.20.0 age confidence devDependencies minor
cbor-x 1.6.51.6.6 age confidence dependencies patch
globals 17.11.017.12.0 age confidence devDependencies minor
msgpackr 2.0.62.1.0 age confidence dependencies minor
node (source) 24.19.024.20.0 age confidence minor
node 24.19.024.20.0 age confidence uses-with minor
openai 7.5.07.8.0 age confidence devDependencies minor 7.10.0 (+1)
oxlint (source) 1.79.01.81.0 age confidence devDependencies minor 1.82.0
papaparse (source) 5.6.05.7.0 age confidence dependencies minor
systeminformation (source) 5.33.15.33.7 age confidence dependencies patch 5.33.9 (+1)
tar-stream 3.2.03.2.1 age confidence dependencies patch
tsx (source) 4.23.124.23.13 age confidence devDependencies patch
typescript-eslint (source) 8.67.08.69.0 age confidence devDependencies minor 8.70.0

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

aws/aws-sdk-js-v3 (@​aws-sdk/client-s3)

v3.1123.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-s3

v3.1122.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-s3

v3.1121.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-s3

v3.1120.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-s3

v3.1119.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-s3

v3.1118.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-s3

v3.1117.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-s3

aws/aws-sdk-js-v3 (@​aws-sdk/lib-storage)

v3.1123.0

Compare Source

Note: Version bump only for package @​aws-sdk/lib-storage

v3.1122.0

Compare Source

Note: Version bump only for package @​aws-sdk/lib-storage

v3.1121.0

Compare Source

Note: Version bump only for package @​aws-sdk/lib-storage

v3.1120.0

Compare Source

Note: Version bump only for package @​aws-sdk/lib-storage

v3.1119.0

Compare Source

Note: Version bump only for package @​aws-sdk/lib-storage

v3.1118.0

Compare Source

Note: Version bump only for package @​aws-sdk/lib-storage

v3.1117.0

Compare Source

Note: Version bump only for package @​aws-sdk/lib-storage

HarperFast/skills (@​harperfast/skills)

v1.12.5

Compare Source

Documentation

v1.12.4

Compare Source

Documentation

v1.12.3

Compare Source

Documentation
typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v8.69.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

See GitHub Releases for more information.

You can read about our versioning strategy and releases on our website.

v8.68.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

See GitHub Releases for more information.

You can read about our versioning strategy and releases on our website.

axios/axios (axios)

v1.20.0

Compare Source

v1.20.0 — August 19, 2026

This release hardens runtime option handling, adds RFC 9110 status-code aliases, fixes Node.js and XHR reliability issues, and refreshes project tooling and documentation.

⚠️ Breaking Changes & Deprecations

  • HTTP Status Naming: Added ContentTooLarge (413) and UnprocessableContent (422), while retaining PayloadTooLarge and UnprocessableEntity as backward-compatible deprecated aliases. (#​11082)

🔒 Security Fixes

  • Runtime Option Handling: Hardened behavioral configuration reads against shared and foreign prototype pollution and normalized unsafe interceptor replacement objects. This also clarifies Fetch redirect and custom implementation behavior, HTTP/2 DNS and proxy handling, CIDR-based NO_PROXY matching, and malformed data URI rejection; see the PR for documented compatibility effects. (#​11141)

🐛 Bug Fixes

  • Interceptor Lifecycle: Prevented unbounded handler-array growth by trimming trailing ejected interceptors without changing iteration semantics, and kept interceptor operations safe when the public handlers field is nullish. (#​11087, #​11118)
  • Request Error Preservation: Prevented custom Error.prepareStackTrace implementations that return non-string values from replacing the original request failure with an unrelated TypeError. (#​11109)
  • XHR Reliability: Navigation-canceled requests now reject with ECONNABORTED instead of resolving with status 0, while successful downloads flush their final progress callback during the live loadend dispatch. (#​11094, #​11121)
  • Node.js Socket Memory: Removed request-context retention from per-socket error listeners, preventing completed response data from being pinned for the lifetime of pooled keep-alive sockets. (#​11091)
  • Core Methods and HTTP Errors: Prevented structural method-header buckets from leaking into outgoing headers, standardized invalid DNS lookup and httpVersion failures as AxiosError.ERR_BAD_OPTION_VALUE, and corrected the timeoutErrorMessage merge strategy. (#​11096)

🔧 Maintenance & Chores

🌟 New Contributors

We are thrilled to welcome our new contributors. Thank you for helping improve axios:

Full Changelog (axios/axios@v1.19.0...v1.20.0)

kriszyp/cbor-x (cbor-x)

v1.6.6

Compare Source

sindresorhus/globals (globals)

v17.12.0

Compare Source


kriszyp/msgpackr (msgpackr)

v2.1.0

Compare Source

nodejs/node (node)

v24.20.0: 2026-08-26, Version 24.20.0 'Krypton' (LTS), @​aduh95

Compare Source

Notable Changes
Commits

Note

PR body was truncated to here.


Configuration

📅 Schedule: (in timezone America/New_York)

  • Branch creation
    • "before 9am on Monday"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Review-Coverage: authored=codex; ran=gemini,claude,cursor-grok; adjudicated=domain; declined=cursor-composer; rounds=12; full=1 @ c23fe61

Human-Review-Need: 4 (decisions: tar-stream-hold-layer, grouped-runtime-upgrades) @ c23fe61

@renovate
renovate Bot enabled auto-merge (squash) September 7, 2026 06:25
@github-actions
github-actions Bot requested a review from kriszyp September 7, 2026 06:26
@socket-security

socket-security Bot commented Sep 7, 2026

Copy link
Copy Markdown

@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 30824ac to a77bee5 Compare September 7, 2026 13:00

@dawsontoth dawsontoth left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Blocking on one package in this batch: tar-stream 3.2.0 → 3.2.1 breaks npm run build. Everything else in the batch is clean. Reproduced and isolated locally (macOS, Node 24.19.0, npm 11.17.0).

The failure

tsc --project tsconfig.build.json exits 2 with 10 errors, all in tar usage:

components/Application.ts(867,26):        TS2345  Extract<ExtractEvents> has no properties in common with PipelineOptions
components/packageComponent.ts(148,16):   TS2339  Property 'on' does not exist on type 'Pack'
components/packageComponent.ts(154,13):   TS2769  'Pack' is not assignable to 'PipelineSource<any>'
dataLayer/rocksdbBackup.ts(752,27):       TS2769  'Pack' is not assignable to 'PipelineSource<any>'
dataLayer/rocksdbBackup.ts(878,9):        TS2339  Property 'end' does not exist on type 'Sink'
dataLayer/rocksdbBackup.ts(899,11):       TS2339  Property 'end' does not exist on type 'Sink'
dataLayer/rocksdbBackup.ts(905,40):       TS2339  Property 'destroy' does not exist on type 'Sink'
dataLayer/rocksdbBackup.ts(906,16):       TS2345  'Sink' is not assignable to 'WritableStream'
dataLayer/rocksdbBackup.ts(919,9):        TS2339  Property 'end' does not exist on type 'Sink'

This is what reddens smoke (linux/amd64, ubuntu-latest) and all three Next.js adapter integration jobs — both build harper from source, so they hit the same tsc.

Isolated to tar-stream, and only tar-stream

Reverting only tar-stream to 3.2.0 on this branch, with every other bump in the batch left in place:

tar-stream tsc --project tsconfig.build.json
3.2.1 (this PR) exit 2, 10 errors
3.2.0 exit 0

Root cause — an upstream packaging change

tar-stream@3.2.1 added index.d.ts to its files array. 3.2.0 shipped no declarations at all, so types came from our @types/tar-stream@^3.1.4, which models Pack/Sink/Extract as Node streams. The new bundled declarations win over @types/*, and they model them as streamx streams instead:

import { Readable, Writable, ... } from 'streamx'
interface Sink extends Writable {}
interface Pack extends Readable { entry(...): Sink; finalize(): void }

Two things go wrong:

  1. streamx@2.23.0 ships no type declarations and there is no @types/streamx in the tree, so Readable/Writable resolve to nothing and Pack/Sink collapse to empty interfaces — hence Property 'end' does not exist on type 'Sink'.
  2. Even with types present, streamx streams are genuinely not Node streams. Installing @types/streamx@2.9.5 takes it from 10 errors to 2, but not to 0 — streamx's Writable.end() returns void where Node's returns this, so node:stream.pipeline() still rejects them:
    dataLayer/rocksdbBackup.ts(906,16): 'Sink' is not assignable to 'WritableStream'
      The types returned by 'end(...)' are incompatible: 'void' is not assignable to 'WritableStream'
    

So deleting @types/tar-stream is not the fix (verified — same 10 errors with it removed), and @types/streamx is only a partial one. The code works at runtime; it is the declarations that regressed. Adapting packageComponent.ts / rocksdbBackup.ts / Application.ts to streamx-typed streams is a real code change, not a Renovate change.

Ask

Please split tar-stream out of this batch — pin it to 3.2.0 (or add a Renovate ignore/pin entry) and let the rest land. I'd rather not hold nine good bumps behind one upstream types regression.

The rest of the batch is verified clean

With tar-stream at 3.2.0 and every other bump from this PR in place (axios 1.20.0, @aws-sdk/client-s3 + lib-storage 3.1121.0, cbor-x 1.6.6, msgpackr 2.1.0, papaparse 5.7.0, systeminformation 5.33.6, openai 7.8.0, oxlint 1.80.0, tsx 4.23.13, typescript-eslint 8.68.0, @harperfast/skills 1.12.4, Node 24.20.0):

  • npm run build — exit 0
  • Unit suite (unitTests/**, minus apiTests/harperBridge/resources and the two tests that hang in a sandbox): 5337 passing / 203 pending / 25 failing, and the base commit 38fcbf1 gives the identical 5337 / 203 / 25 with a byte-identical failure set. Zero PR-only failures.
  • SQL suites (sqlTranslator, sqlEngine, dataLayer/sql-update, dataLayer/SQLSearch, utility/functions/sql/alaSQLExtension): 258 passing / 8 pending / 0 failing, same as base.

Not caused by this PR

Unit Test (Node.js v22/v24/v26) are red on subscribe to retained record with patch operations (unitTests/apiTests/mqtt-test.mjs:503, AssertionError: 'update 3' == 'update 2'). That is a main defect, not yours: #2516 (alasql only) fails identically on all three Node versions, and so does #2476, an unrelated feature PR run against the same base this morning. Filing separately — don't chase it here.

@renovate

renovate Bot commented Sep 8, 2026

Copy link
Copy Markdown
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@dawsontoth

Copy link
Copy Markdown
Contributor

Status update after the branch moved — the tar-stream 3.2.0 → 3.2.1 block still stands, unchanged.

Kris merged main into this branch at 15:58 (91758142). That did not clear it, and I want to flag that explicitly so nobody reads the merge as having addressed the review.

Still failing on the current head

smoke and all three Next.js adapter integration jobs re-ran against 91758142 and produced the identical 10 tsc errors:

components/Application.ts(867,26):      TS2345  Extract<ExtractEvents> ... not assignable to PipelineOptions
components/packageComponent.ts(148,16): TS2339  Property 'on' does not exist on type 'Pack'
components/packageComponent.ts(154,13): TS2769  'Pack' is not assignable to 'PipelineSource<any>'
dataLayer/rocksdbBackup.ts(752,27):     TS2769  'Pack' is not assignable to 'PipelineSource<any>'
dataLayer/rocksdbBackup.ts(878,9):      TS2339  Property 'end' does not exist on type 'Sink'
dataLayer/rocksdbBackup.ts(899,11):     TS2339  Property 'end' does not exist on type 'Sink'
dataLayer/rocksdbBackup.ts(905,40):     TS2339  Property 'destroy' does not exist on type 'Sink'
dataLayer/rocksdbBackup.ts(906,16):     TS2345  'Sink' is not assignable to 'WritableStream'
dataLayer/rocksdbBackup.ts(919,9):      TS2339  Property 'end' does not exist on type 'Sink'

Why it's easy to miss in the diff

The bump is not visible in the package.json diff"tar-stream": "^3.1.8" is byte-identical on main and on this branch. It moved in the lockfile only:

ref node_modules/tar-stream
main 3.2.0
renovate/all-minor-patch 3.2.1

So a reviewer scanning the manifest diff (axios, @aws-sdk/lib-storage, cbor-x, msgpackr, papaparse, plus the 24.19.0 → 24.20.0 Node bump) sees nothing wrong. The regression is entirely inside the ^3.1.8 range.

Root cause is unchanged from my review above: tar-stream@3.2.1 added index.d.ts to its files array. 3.2.0 shipped no declarations, so @types/tar-stream@^3.1.4 supplied them and modeled Pack/Sink/Extract as Node streams; the new bundled declarations take precedence over @types/* and model them as streamx types instead. Nothing in our source changed.

Ask, unchanged

Hold tar-stream at 3.2.0. The rest of the batch is clean and I'd like it to land. Since the range in package.json already permits 3.2.1, a rebase will just re-resolve it — this needs a Renovate rule on main to stick:

{
  "description": "Hold tar-stream on 3.2.0: 3.2.1 added a bundled index.d.ts that overrides @types/tar-stream and models Pack/Sink/Extract as streamx rather than Node streams, breaking `tsc --project tsconfig.build.json` in 10 places. Neither removing @types/tar-stream nor pinning it fixes it. Drop once our tar usage is ported to the streamx types.",
  "matchPackageNames": ["tar-stream"],
  "allowedVersions": "<3.2.1"
}

There's no such rule in renovate.json on main today. Without it this will come back on the next run, the same way the agent lockfile issue has now recurred seven times.

One note for whoever picks this up: Renovate has already posted its "will not automatically rebase … does not recognize the last commit author" notice because of the merge commit, so ticking the rebase box will discard it. Better to add the rule to main and let Renovate regenerate cleanly.

@kriszyp
kriszyp marked this pull request as draft September 14, 2026 04:48
auto-merge was automatically disabled September 14, 2026 04:48

Pull request was converted to draft

renovate Bot and others added 5 commits September 14, 2026 05:39
Co-Authored-By: GPT-5.6 Sol <noreply@openai.com>
Co-Authored-By: GPT-5.6 Sol <noreply@openai.com>
Co-Authored-By: GPT-5.6 Sol <noreply@openai.com>
Co-Authored-By: GPT-5.6 Sol <noreply@openai.com>
@kriszyp
kriszyp force-pushed the renovate/all-minor-patch branch from c23fe61 to de02862 Compare September 14, 2026 13:10

@dawsontoth dawsontoth left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My tar-stream block is resolved — clearing the changes-requested. fe35e4fe pins the manifest at 3.2.0 (tightening ^3.1.8 to an exact pin, which is the right call for a package whose packaging regressed) and 3405afa2 adds the Renovate hold so it doesn't come straight back. Verified on the current head de028627:

npm ci         exit 0
npm run build  exit 0     ← was exit 2 with 10 tsc errors

Unit suite: no regressions

PR   de028627   5505 passing / 208 pending / 25 failing
base 1496a18e   5505 passing / 208 pending / 25 failing

Set-diffed the failure titles: zero PR-only failures, zero base-only failures. The 25 are the usual sandbox-blocked categories here.

de028627 reviewed on its own

It is metadata-only — it drops "dev": true / "peer": true from the twelve @cbor-extract/* and @msgpackr-extract/* platform packages. No versions move, nothing is added or removed. Given cbor-x 1.6.5 → 1.6.6 and msgpackr 2.0.6 → 2.1.0 are in this batch, keeping the native accelerators pinned in the published shrinkwrap rather than dev-scoped is correct.

All three red checks are infrastructure, not this PR

I chased each one to its actual cause:

Integration Tests 2/6 (uWS HTTP) — died 25s in, before a single test ran:

npm error code ECONNRESET
npm error network aborted

No test log was even produced (No files were found with the provided path). Pure registry flake.

Integration Tests 2/6 (Windows, Node.js v24)The action 'Run Integration Test Shard 2' has timed out after 20 minutes. No assertion failure anywhere in the log.

HNSW native plane (Node.js v24) — one test, vectorIndexPlane.test.js:521, timing out against its 15s waitFor budget. This one I took seriously, because msgpackr/cbor-x are exactly the codecs a derived-mapping rebuild runs through. It does not hold up:

where rebuilds from primary records when its durable cursor is outside audit retention
main 1496a18e (run 34838615153) ✔ 1054 ms
main eec839ee (run 34805593428) ✔ 1025 ms
main 4d375bfe (run 34791149457) ✔ 1025 ms
this PR head de028627, run locally ✔ 1053 ms (22 passing)
this PR head, CI run 34847573728 ✖ blew 15 000 ms

Ran the whole vectorIndexPlane.test.js file locally on de028627 with the shrinkwrap change in place — 22/22 passing, and the test in question lands at 1053 ms, within 1% of what main does. A test that normally finishes in ~1s doesn't miss a 15s deadline because of a codec change; it does that because the runner stalled. The same run's benchmark neighbour degraded from 4919/s to 3473/s as it went, which is what a starved runner looks like.

Please just re-run those three jobs — there is nothing here to fix in the branch.

Approving.

@dawsontoth

Copy link
Copy Markdown
Contributor

Status nudge — my approval from the 14th still stands, and nothing about this PR has changed since. Head is still de028627; I'm not re-running the suite for a branch that hasn't moved. Two things are worth flagging, though, because this is now sitting idle:

  1. The three red checks have not been re-run in four days. I traced each to the runner rather than the branch in my approval above (uWS = ECONNRESET before any test ran, Windows shard 2 = 20-minute action timeout with no assertion failure, HNSW = a test that lands at 1053 ms locally blowing a 15 s budget). A re-run is all that's needed; mergeStateStatus is UNSTABLE purely because of them.

  2. The branch is now 124 commits behind main. Still MERGEABLE, no conflicts, but the green shards are validating a four-day-old merge base. If the re-run happens after a main merge rather than before, that's strictly better.

I also re-checked whether the tar-stream pin can be relaxed yet: it cannot. 3.2.1 is still the latest publish (2026-08-25), there is no 3.2.2, so fe35e4fe's exact pin at 3.2.0 and the Renovate hold both still need to stay.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants