Skip to content

deps: periodic dependency update#6099

Merged
qw-in merged 6 commits into
mainfrom
quinn/deps-2026-06-26
Jun 26, 2026
Merged

deps: periodic dependency update#6099
qw-in merged 6 commits into
mainfrom
quinn/deps-2026-06-26

Conversation

@qw-in

@qw-in qw-in commented Jun 26, 2026

Copy link
Copy Markdown
Member

No description provided.

qw-in and others added 4 commits June 26, 2026 12:12
Routine minor/patch refresh across the workspace, honoring the repo's
Renovate policy: 7-day cooldown (newer releases held back), the
@bytecodealliance/jco <=1.5.0 and @types/node <23 pins, and library
peer-dependency ranges left untouched.

Updated (dev tooling + the @connectrpc/connect runtime patch):
@rollup/wasm-node 4.61.0→4.62.2, turbo 2.9.16→2.9.18,
typescript-eslint 8.57.2→8.61.1, eslint-config-turbo 2.8.20→2.9.18,
@connectrpc/connect{,-node,-web} 2.1.1→2.1.2, next 16.2.6→16.2.9,
svelte 5.55.7→5.56.3, @sveltejs/kit 2.60.1→2.66.0,
@sveltejs/vite-plugin-svelte 7.0.0→7.1.2, react{,-dom} 19.2.4→19.2.7,
react-router 7.16.0→7.18.0, @nestjs/common 11.1.17→11.1.27,
@nuxt/{kit,schema} 4.4.2→4.4.8, astro 6.4.6→6.4.8,
undici-types 7.27.0→7.28.0.

npm audit unchanged from baseline (6 pre-existing, Dependabot's lane).
Leaf packages build, lint, and test clean with the new tooling; the
protocol/analyze rollup-typescript build fails on a pre-existing
workspace type-resolution quirk (identical toolchain versions to main) —
CI is the gate for those.

Co-Authored-By: Claude <noreply@anthropic.com>
arcjet-guard has its own lockfile (excluded from the workspace). Routine
minor/patch refresh of build tooling, 7-day cooldown respected:
rolldown 1.0.3→1.1.2, rolldown-plugin-dts 0.25.2→0.26.0,
miniflare 4.20260617.0→4.20260617.1.

Runtime dependency ranges (@bufbuild/protobuf, @connectrpc/* at ^2.0.0)
left untouched — they already allow the latest, and bumping the floor of
a library's runtime range needlessly narrows consumer compatibility. The
pinned @typescript/native-preview (tsgo) is left for a deliberate
toolchain update.

Validated: build, lint, and 267 unit tests pass.

Co-Authored-By: Claude <noreply@anthropic.com>
oxfmt 0.53.0→0.55.0 (7-day cooldown; 0.56.0 held back). Reformats two
source files (a wrapped line that now fits). Adds CHANGELOG.md to the
oxfmt ignorePatterns — it is generated by release-please and should not
be reformatted (it was being flagged by format:check before this).

Formatting only; no behavior change. build, lint, and 267 unit tests
pass; format:check is now clean.

Co-Authored-By: Claude <noreply@anthropic.com>
oxlint 1.58.0→1.70.0, oxlint-tsgolint 0.18.1→0.23.0 (7-day cooldown
respected; oxlint 1.71.0 held back).

oxlint 1.70 newly enforces several pedantic/stylistic rules that were
not active under 1.58 (lint was clean before). They produce ~280
detections across the codebase — none are bugs:
prefer-readonly-parameter-types (~200), require-unicode-regexp (~25),
consistent-return, strict-void-return, no-unnecessary-type-parameters,
and no-underscore-dangle (the latter conflicts with the SDK's deliberate
_internal naming).

Disabled those six rules in .oxlintrc.json with a TODO so the linter
bump lands now without 280 inline suppressions. Adopting the rules is a
deliberate code change tracked separately (see PR/issue note). lint,
build, and 267 unit tests pass.

Co-Authored-By: Claude <noreply@anthropic.com>
@qw-in qw-in self-assigned this Jun 26, 2026
@qw-in qw-in requested a review from a team as a code owner June 26, 2026 19:26

@arcjet-review arcjet-review Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Arcjet Review — 🟡 Medium Risk

Decision: Approved

Rationale: This PR is a broad periodic dependency update across many package.json files, which triggers dependency-change review. The updates appear to be pinned exact-version patch/minor bumps to established packages, with no new dependencies introduced and no substantive application logic changes beyond formatting. Security review found no hardcoded secrets, auth changes, injection surfaces, cryptography changes, or user-input handling changes. I am approving despite Medium risk because the dependency changes are well-scoped and low-risk individually, but CI/build/test results should still be checked closely.

Summary of Changes

Updates Rollup wasm, framework/dev tooling packages, ConnectRPC packages, Turbo, and arcjet-guard tooling versions; adjusts oxlint/oxfmt config for newly enforced stylistic rules; includes minor formatting-only TypeScript changes.

Escalation Triggers

  • Dependency Changes: Multiple package.json files were modified with dependency and devDependency version updates across the monorepo.

Review Focus Areas

Notes

No size-threshold concern identified from the provided diff.

Path filtering: 2 files excluded by ignore paths. 41 of 43 files included in review.

Review: 1802e4ee | Model: openai/gpt-5.5 | Powered by Arcjet Review

Comment thread arcjet-guard/.oxlintrc.json
Comment thread package.json
@socket-security

socket-security Bot commented Jun 26, 2026

Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: npm @emnapi/runtime is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: arcjet-guard/package-lock.jsonnpm/rolldown@1.1.2npm/miniflare@4.20260617.1npm/@emnapi/runtime@1.11.1

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@emnapi/runtime@1.11.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm @typescript-eslint/eslint-plugin is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: package-lock.jsonnpm/typescript-eslint@8.61.1npm/@typescript-eslint/eslint-plugin@8.61.1

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@typescript-eslint/eslint-plugin@8.61.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm astro is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: arcjet-astro/package.jsonnpm/astro@6.4.8

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/astro@6.4.8. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

qw-in and others added 2 commits June 26, 2026 12:34
Regenerate the root npm lockfile after restoring it from main.

arcjet-guard/package-lock.json was also restored from main and regenerated from its separate workspace; npm produced no resulting diff there.

Co-authored-by: Codex <codex@openai.com>
Skip the optimistic HTTP/2 warmup when running under Deno so background node:http2 session failures are not reported as uncaught test errors.

Actual request failures still surface through the request path, and Node keeps the existing preconnect behavior.

Co-authored-by: Codex <codex@openai.com>
@qw-in qw-in added this pull request to the merge queue Jun 26, 2026
Merged via the queue into main with commit 6acea2e Jun 26, 2026
52 checks passed
@qw-in qw-in deleted the quinn/deps-2026-06-26 branch June 26, 2026 21:54
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.

1 participant