Skip to content

chore(deps-dev): bump the development group across 1 directory with 5 updates#27

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/development-ca08c454b9
Open

chore(deps-dev): bump the development group across 1 directory with 5 updates#27
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/development-ca08c454b9

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 8, 2026

Copy link
Copy Markdown
Contributor

Bumps the development group with 5 updates in the / directory:

Package From To
@types/node 26.0.1 26.1.0
oxfmt 0.56.0 0.57.0
oxlint 1.71.0 1.72.0
oxlint-tsgolint 0.23.0 0.24.0
vitest 4.1.9 4.1.10

Updates @types/node from 26.0.1 to 26.1.0

Commits

Updates oxfmt from 0.56.0 to 0.57.0

Commits

Updates oxlint from 1.71.0 to 1.72.0

Release notes

Sourced from oxlint's releases.

oxlint v1.27.0 && oxfmt v0.12.0

Oxlint v1.27.0

🚀 Features

  • 222a8f0 linter/plugins: Implement SourceCode#isSpaceBetween (#15498) (overlookmotel)
  • 2f9735d linter/plugins: Implement context.languageOptions (#15486) (overlookmotel)
  • bc731ff linter/plugins: Stub out all Context APIs (#15479) (overlookmotel)
  • 5822cb4 linter/plugins: Add extend method to FILE_CONTEXT (#15477) (overlookmotel)
  • 7b1e6f3 apps: Add pure rust binaries and release to github (#15469) (Boshen)
  • 2a89b43 linter: Introduce debug assertions after fixes to assert validity (#15389) (camc314)
  • ad3c45a editor: Add oxc.path.node option (#15040) (Sysix)

🐛 Bug Fixes

  • 6f3cd77 linter/no-var: Incorrect warning for blocks (#15504) (Hamir Mahal)
  • 6957fb9 linter/plugins: Do not allow access to Context#id in createOnce (#15489) (overlookmotel)
  • 7409630 linter/plugins: Allow access to cwd in createOnce in ESLint interop mode (#15488) (overlookmotel)
  • 732205e parser: Reject using / await using in a switch case / default clause (#15225) (sapphi-red)
  • a17ca32 linter/plugins: Replace Context class (#15448) (overlookmotel)
  • ecf2f7b language_server: Fail gracefully when tsgolint executable not found (#15436) (camc314)
  • 3c8d3a7 lang-server: Improve logging in failure case for tsgolint (#15299) (camc314)
  • ef71410 linter: Use jsx if source type is JS in fix debug assertion (#15434) (camc314)
  • e32bbf6 linter/no-var: Handle TypeScript declare keyword in fixer (#15426) (camc314)
  • 6565dbe linter/switch-case-braces: Skip comments when searching for : token (#15425) (camc314)
  • 85bd19a linter/prefer-class-fields: Insert value after type annotation in fixer (#15423) (camc314)
  • fde753e linter/plugins: Block access to context.settings in createOnce (#15394) (overlookmotel)
  • ddd9f9f linter/forward-ref-uses-ref: Dont suggest removing wrapper in invalid positions (#15388) (camc314)
  • dac2a9c linter/no-template-curly-in-string: Remove fixer (#15387) (camc314)
  • 989b8e3 linter/no-var: Only fix to const if the var has an initializer (#15385) (camc314)
  • cc403f5 linter/plugins: Return empty object for unimplemented parserServices (#15364) (magic-akari)

⚡ Performance

  • 25d577e language_server: Start tools in parallel (#15500) (Sysix)
  • 3c57291 linter/plugins: Optimize loops (#15449) (overlookmotel)
  • 3166233 linter/plugins: Remove Arcs (#15431) (overlookmotel)
  • 9de1322 linter/plugins: Lazily deserialize settings JSON (#15395) (overlookmotel)
  • 3049ec2 linter/plugins: Optimize deepFreezeSettings (#15392) (overlookmotel)
  • 444ebfd linter/plugins: Use single object for parserServices (#15378) (overlookmotel)

📚 Documentation

  • 97d2104 linter: Update comment in lint.rs about default value for tsconfig path (#15530) (Connor Shea)
  • 2c6bd9e linter: Always refer as "ES2015" instead of "ES6" (#15411) (sapphi-red)
  • a0c5203 linter/import/named: Update "ES7" comment in examples (#15410) (sapphi-red)
  • 3dc24b5 linter,minifier: Always refer as "ES Modules" instead of "ES6 Modules" (#15409) (sapphi-red)
  • 2ad77fb linter/no-this-before-super: Correct "Why is this bad?" section (#15408) (sapphi-red)
  • 57f0ce1 linter: Add backquotes where appropriate (#15407) (sapphi-red)

Oxfmt v0.12.0

... (truncated)

Changelog

Sourced from oxlint's changelog.

[1.72.0] - 2026-06-29

🚀 Features

  • 1c8f50c linter: Add schema for eslint/no-restricted-import (#23642) (Sysix)

🐛 Bug Fixes

  • 742be36 refactor/node/handle-callback-err: Reject invalid regex config (#23740) (camc314)
Commits

Updates oxlint-tsgolint from 0.23.0 to 0.24.0

Release notes

Sourced from oxlint-tsgolint's releases.

v0.24.0

What's Changed

... (truncated)

Commits
  • 5a37e89 fix(dot-notation): determine the relevant accessor (#1028)
  • 67a281f perf(consistent-return): defer per-function type resolution (#1031)
  • a5e2ff0 perf(no-unnecessary-qualifier): skip symbol resolution outside namespaces. (#...
  • a8fc668 perf(no-confusing-void-expression): check ancestor position before type query...
  • 03158cc perf(no-unnecessary-type-conversion): hoist constant builtin-name slices (#1040)
  • d9e645c perf(prefer-optional-chain): lazily allocate chain-processor caches (#1041)
  • 63f578a refactor(no-unnecessary-condition): remove dead containsUnguardedElementAcces...
  • f174876 chore(deps): update gomod (#1035)
  • 47de9cf chore(deps): update github actions (#1036)
  • e209b5b chore(deps): update actions/cache action to v6 (#1037)
  • Additional commits viewable in compare view

Updates vitest from 4.1.9 to 4.1.10

Release notes

Sourced from vitest's releases.

v4.1.10

   🐞 Bug Fixes

    View changes on GitHub
Commits
  • db616d2 chore: release v4.1.10 (#10718)
  • bae52b5 fix(vm): fix external module resolve error with deps optimizer query for enco...
  • See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

@dependabot
chore(deps-dev): bump the development group across 1 directory with 5…
9153589 
… updates

Bumps the development group with 5 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) | `26.0.1` | `26.1.0` |
| [oxfmt](https://github.com/oxc-project/oxc/tree/HEAD/npm/oxfmt) | `0.56.0` | `0.57.0` |
| [oxlint](https://github.com/oxc-project/oxc/tree/HEAD/npm/oxlint) | `1.71.0` | `1.72.0` |
| [oxlint-tsgolint](https://github.com/oxc-project/tsgolint) | `0.23.0` | `0.24.0` |
| [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) | `4.1.9` | `4.1.10` |



Updates `@types/node` from 26.0.1 to 26.1.0
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node)

Updates `oxfmt` from 0.56.0 to 0.57.0
- [Release notes](https://github.com/oxc-project/oxc/releases)
- [Changelog](https://github.com/oxc-project/oxc/blob/main/npm/oxfmt/CHANGELOG.md)
- [Commits](https://github.com/oxc-project/oxc/commits/oxfmt_v0.57.0/npm/oxfmt)

Updates `oxlint` from 1.71.0 to 1.72.0
- [Release notes](https://github.com/oxc-project/oxc/releases)
- [Changelog](https://github.com/oxc-project/oxc/blob/main/npm/oxlint/CHANGELOG.md)
- [Commits](https://github.com/oxc-project/oxc/commits/oxlint_v1.72.0/npm/oxlint)

Updates `oxlint-tsgolint` from 0.23.0 to 0.24.0
- [Release notes](https://github.com/oxc-project/tsgolint/releases)
- [Commits](oxc-project/tsgolint@v0.23.0...v0.24.0)

Updates `vitest` from 4.1.9 to 4.1.10
- [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.10/packages/vitest)

---
updated-dependencies:
- dependency-name: "@types/node"
  dependency-version: 26.1.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: development
- dependency-name: oxfmt
  dependency-version: 0.57.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: development
- dependency-name: oxlint
  dependency-version: 1.72.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: development
- dependency-name: oxlint-tsgolint
  dependency-version: 0.24.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: development
- dependency-name: vitest
  dependency-version: 4.1.10
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: development
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Jul 8, 2026
@socket-security

socket-security Bot commented Jul 8, 2026

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security		 Vulnerability Quality Maintenance License
Addedoxfmt@​0.57.0691008995100
Addedvitest@​4.1.10981007999100
Added@​types/​node@​26.1.01001008196100
Addedoxlint@​1.72.0911009295100
Addedoxlint-tsgolint@​0.24.01001009794100

View full report

@socket-security

socket-security Bot commented Jul 8, 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 oxfmt is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: package.json → npm/oxfmt@0.57.0

ℹ 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/oxfmt@0.57.0. 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 oxfmt is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: package.json → npm/oxfmt@0.57.0

ℹ 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/oxfmt@0.57.0. 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

@clawsweeper

clawsweeper Bot commented Jul 8, 2026 •
edited
Loading

Copy link
Copy Markdown

Codex review: needs maintainer review before merge. Reviewed July 8, 2026, 1:19 PM ET / 17:19 UTC.

Summary
The PR bumps five direct development dependencies and refreshes package.json plus pnpm-lock.yaml for the updated formatter, linter, type, and test tooling versions.

Reproducibility: not applicable. this is a dependency-bump PR rather than a bug report. The relevant checks are the package/lockfile diff, CI status, and Socket supply-chain comments.

Review metrics: 3 noteworthy metrics.

  • Direct dev updates: 5 updates. The PR batches formatter, linter, type, and test-tool changes, so one alert affects the whole grouped merge decision.
  • Files changed: 2 files, 273 additions, 267 deletions. The code surface is limited to package.json and the generated pnpm lockfile.
  • Native toolchain packages: 3 updated. oxfmt, oxlint, and oxlint-tsgolint ship platform-specific binaries that can execute in local or CI tooling paths.

Merge readiness
Overall: 🦐 gold shrimp
Proof: 🌊 off-meta tidepool
Patch quality: 🦐 gold shrimp
Result: ready for maintainer review.

Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch.

Rank-up moves:

  • Have a maintainer accept the oxfmt@0.57.0 warning or split/defer that dependency update.

Risk before merge

  • [P1] Socket reported high-severity obfuscated-code warnings for npm oxfmt@0.57.0; green CI does not prove that the new formatter package is acceptable supply-chain risk.
  • [P1] The lockfile refresh updates multiple platform-specific native toolchain packages that run during install, formatting, linting, or tests, so merge should wait for explicit risk acceptance or a split update.

Maintainer options:

  1. Split the flagged formatter bump (recommended)
    Keep the low-risk dependency updates moving while excluding oxfmt@0.57.0 until the package warning is gone or separately accepted.
  2. Accept the package warning
    A maintainer may intentionally accept the Socket alert after reviewing the new oxfmt release and leave the PR as-is.
  3. Pause this batch
    If the grouped update is not worth the supply-chain review cost, close it and wait for a safer Dependabot refresh.

Next step before merge

  • [P2] A maintainer/security review should decide whether to accept, split, or defer the flagged oxfmt update; there is no narrow code repair for automation to apply safely.

Maintainer decision needed

  • Question: Should maintainers accept the Socket obfuscated-code warning for oxfmt@0.57.0 in this dev-tooling bump, or require the update to be split/deferred?
  • Rationale: The PR is mechanically clean, but accepting a new formatter package with a high-severity supply-chain warning is a repository risk decision that automation should not make.
  • Likely owner: Vincent Koc — They introduced the package tooling and release validation surface affected by the dependency update.
  • Options:
    • Split or defer oxfmt (recommended): Ask for a narrower update that excludes oxfmt@0.57.0, or wait for a later oxfmt release without this warning while keeping the rest of the bump reviewable.
    • Accept after review: Merge this PR only after a maintainer reviews the oxfmt package provenance/source and explicitly accepts the Socket warning as tolerable.
    • Close and let Dependabot retry: Close this batch if maintainers prefer a future Dependabot PR with a different dependency set or resolved alert.

Security
Needs attention: The diff is narrow, but Socket flagged the new oxfmt@0.57.0 dependency with high-severity obfuscated-code warnings that need maintainer review before merge.

Review details

Best possible solution:

Merge only after maintainers explicitly accept the oxfmt@0.57.0 warning or split/defer that package while landing any low-risk dependency updates separately.

Do we have a high-confidence way to reproduce the issue?

Not applicable; this is a dependency-bump PR rather than a bug report. The relevant checks are the package/lockfile diff, CI status, and Socket supply-chain comments.

Is this the best way to solve the issue?

Unclear until the oxfmt warning is resolved or accepted. The mechanical update is narrow and CI is green, but the best merge path should avoid silently accepting the flagged package.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 95630872f37a.

Label changes

Label changes:

  • add P2: This is a normal dependency-maintenance PR with limited runtime blast radius, but it needs maintainer attention because of a concrete supply-chain warning.
  • add merge-risk: 🚨 other: Merging would accept a new dev-tooling package version that Socket flagged as likely obfuscated, which is a supply-chain risk outside normal CI correctness.
  • add rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🌊 off-meta tidepool and patch quality is 🦐 gold shrimp.
  • add status: ⏳ waiting on author: ClawSweeper has contributor-facing work open and is waiting for author action. Not applicable: This is a Dependabot bot dependency PR, so contributor real-behavior proof is not required; CI is supplemental validation only.

Label justifications:

  • P2: This is a normal dependency-maintenance PR with limited runtime blast radius, but it needs maintainer attention because of a concrete supply-chain warning.
  • merge-risk: 🚨 other: Merging would accept a new dev-tooling package version that Socket flagged as likely obfuscated, which is a supply-chain risk outside normal CI correctness.
  • rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🌊 off-meta tidepool and patch quality is 🦐 gold shrimp.
  • status: ⏳ waiting on author: ClawSweeper has contributor-facing work open and is waiting for author action. Not applicable: This is a Dependabot bot dependency PR, so contributor real-behavior proof is not required; CI is supplemental validation only.
Evidence reviewed

Security concerns:

  • [high] Review the flagged oxfmt package before merge — package.json:94
    The PR updates oxfmt to 0.57.0 and refreshes many native binding hashes; Socket reports the package as 90% likely obfuscated, so this should be explicitly accepted, split out, or deferred.
    Confidence: 0.9

What I checked:

  • Repository policy read: AGENTS.md was read fully; its pnpm/package-script and dependency-lockfile guidance applies to this package/lockfile PR. (AGENTS.md:17, 95630872f37a)
  • Dependency diff: The PR changes package.json to bump oxfmt from ^0.56.0 to ^0.57.0 and oxlint-tsgolint from ^0.23.0 to ^0.24.0; the PR body also lists @types/node, oxlint, and vitest lockfile updates. (package.json:94, 91535890fdfc)
  • Current main still has old versions: Current main still pins oxfmt 0.56.0, oxlint 1.71.0, oxlint-tsgolint 0.23.0, @types/node 26.0.1, and vitest 4.1.9 in the lockfile, so the PR is not implemented on main. (pnpm-lock.yaml:18, 95630872f37a)
  • Socket warning: Socket posted two high-severity Warn alerts saying npm oxfmt@0.57.0 is 90% likely obfuscated, both sourced from the package.json dependency update.
  • CI state: GitHub reports the PR as mergeable/CLEAN, with the Node 22/24 matrix, CodeQL, workflow lint, Ghostty browser smoke, and Socket checks completed successfully. (91535890fdfc)
  • Tooling history: git blame and git log show Vincent Koc introduced the package scripts and original dev-tooling surface, while Dependabot has recent merged dependency bumps in the same files. (package.json:72, af898fe0cdd3)

Likely related people:

  • Vincent Koc: Blame and history show this person introduced the package scripts/devDependency surface and later hardened release validation, making them the best human route for package-tooling risk decisions. (role: introduced tooling and release setup; confidence: high; commits: af898fe0cdd3, c1ca6f199108, 402f019f2b17; files: package.json, pnpm-lock.yaml)
  • dependabot[bot]: Recent merged dependency-bump commits on current main updated package.json and pnpm-lock.yaml before this PR, including the current @typescript/native-preview and prior development-tooling bumps. (role: recent dependency automation; confidence: medium; commits: 95630872f37a, 2aae4e95db60, 1dcef4535cb1; files: package.json, pnpm-lock.yaml)
What the crustacean ranks mean
  • 🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
  • 🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
  • 🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
  • 🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
  • 🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
  • 🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
  • 🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

How this review workflow works
  • ClawSweeper keeps one durable marker-backed review comment per issue or PR.
  • Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
  • A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
  • PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
  • Maintainers can also comment @clawsweeper review to request a fresh review only.
  • Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
  • Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
  • Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

@clawsweeper clawsweeper Bot added rating: 🦐 gold shrimp Decent PR readiness signal, but merge confidence is limited. status: ⏳ waiting on author ClawSweeper has contributor-facing work open and is waiting for author action. P2 Normal priority bug or improvement with limited blast radius. merge-risk: 🚨 other 🚨 Merging this PR has meaningful risk outside the owned taxonomy. labels Jul 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code merge-risk: 🚨 other 🚨 Merging this PR has meaningful risk outside the owned taxonomy. P2 Normal priority bug or improvement with limited blast radius. rating: 🦐 gold shrimp Decent PR readiness signal, but merge confidence is limited. status: ⏳ waiting on author ClawSweeper has contributor-facing work open and is waiting for author action.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants