Skip to content

chore: Bump the toolchain group across 1 directory with 4 updates - #651

Open
dependabot[bot] wants to merge 2 commits into
trunkfrom
dependabot/npm_and_yarn/toolchain-820c5deaab
Open

dependabot[bot] wants to merge 2 commits into
trunkfrom
dependabot/npm_and_yarn/toolchain-820c5deaab

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

Bumps the toolchain group with 4 updates in the / directory: @effect/tsgo, @vitest/coverage-istanbul, vite-plus and vitest.

Updates @effect/tsgo from 0.69.0 to 0.70.0

Release notes

Sourced from @​effect/tsgo's releases.

@​effect/tsgo@​0.70.0

Minor Changes

  • 9ada5da: Add the flatMapProvideServiceToProvideServiceEffect suggestion in style. An Effect.flatMap (or Effect.andThen given a callback) whose callback only forwards its parameter to Effect.provideService is a manual Effect.provideServiceEffect. The rule reports it in every spelling: pipeable, data-first, pipe(...) and curried, on both the outer flatMap and the inner provideService, and inside Effect.gen / Effect.fn bodies.

    makeConnection.pipe(Effect.flatMap((conn) => Effect.provideService(program, Database, conn))) // reported
    Effect.provideServiceEffect(program, Database, makeConnection)                                // ok

    A quick fix rewrites the expression to Effect.provideServiceEffect(self, Key, acquire) and keeps any later pipe steps: Effect.suspend(() => step(s)).pipe(Effect.flatMap((meta) => Effect.provideService(effect, Key, meta)), Effect.map(f)) becomes Effect.provideServiceEffect(effect, Key, Effect.suspend(() => step(s))).pipe(Effect.map(f)).

    The callback is not reported when it does anything else: when the parameter appears outside the service argument (in the program, in any earlier step of the program, or in the key), when the program or key uses something the callback binds (the name of a named function expression, or a function-expression callback's own this, super, new.target or arguments, plain or as shorthand { arguments }), when the service argument is not the bare parameter, when steps follow provideService, when the acquired value's type is not assignable to the key's service type (for example through a (conn: any) parameter), or when the flatMap result type differs from the provideServiceEffect one (a return-type annotation on the callback or explicit type arguments that widen it, or explicit type arguments on provideService), since code after it may rely on that type. After the fix, the program expression is evaluated once when the expression is built rather than on every run of the callback. The Effect.gen form (const p = yield* acquire; return yield* Effect.provideService(self, Key, p)) is deliberately not reported. On Effect v3, data-first Effect.andThen(acquire, callback) is not reported, since its overloads do not form a dual. The rule supports Effect v3 and v4.

    Piping-flow fixes can now build an expression for a flow prefix with PipingFlowPrefixExpression, including prefixes that end inside a .pipe(...) or pipe(...) call.

  • 50c28e5: Add the forLoopPushToForEach diagnostic (style, off by default; enable it with "forLoopPushToForEach": "suggestion") and quickfix. Inside an Effect generator, a for (const x of iterable) loop whose only statement is acc.push(yield* effect), with acc a const acc = [] declared just before the loop, is reported. The fix replaces it with Effect.forEach. The fix is not offered when the accumulator is mutated after the loop, or when the loop binding or the yielded expression contains a yield of the generator. The callback is passed directly only when it is a plain single-parameter function applied to the loop variable, whether as f(x), pipe(x, f) or x.pipe(f); otherwise an arrow is kept.

    // before
    const results = []
    for (const item of items) {
      results.push(yield* processItem(item))
    }
    // after
    const results = yield* Effect.forEach(items, processItem)

Patch Changes

  • 75a36b2: Update the TypeScript next tag to typescript@next, which ships typescript-go commit 6bdcb54d23f41bc7098c1f3488ac599c75b852ca, update the TypeScript beta tag to typescript@beta, and update the TypeScript latest tag to typescript@latest. Refresh the Oxlint configuration schema from the selected package.

  • 9ada5da: manualMetricTapToTrack now decides more precisely whether a function-expression callback can become an arrow mapper. It looks for the callback's own this, super, new.target, arguments and name the way the compiler resolves them, through the new typeparser helper UsesFunctionOwnBindings, which flatMapProvideServiceToProvideServiceEffect now uses too.

    The rule now reports callbacks it used to skip, since none of these read a binding of the callback:

    Effect.tap(function(size) { return Metric.update(responseSize, size + sizes.arguments) })       // a property named `arguments`
    Effect.tap(function(size) { return Metric.update(responseSize, size + import.meta.url.length) }) // `import.meta`
    Effect.tap(function(size) {                                                                     // a class that uses its own `this` and `arguments`
      return Metric.update(responseSize, size + new (class { readonly n = this; m() { return arguments.length } })().m())
    })

    It no longer reports a named callback that reads its own name through a shorthand property, which the fix would have left unbound:

    Effect.tap(function record(size) { return Metric.update(responseSize, size + Object.keys({ record }).length) })

    Class expressions are still skipped when their extends clause, a computed member name or a member decorator reads the callback's bindings.

... (truncated)

Changelog

Sourced from @​effect/tsgo's changelog.

0.70.0

Minor Changes

  • 9ada5da: Add the flatMapProvideServiceToProvideServiceEffect suggestion in style. An Effect.flatMap (or Effect.andThen given a callback) whose callback only forwards its parameter to Effect.provideService is a manual Effect.provideServiceEffect. The rule reports it in every spelling: pipeable, data-first, pipe(...) and curried, on both the outer flatMap and the inner provideService, and inside Effect.gen / Effect.fn bodies.

    makeConnection.pipe(Effect.flatMap((conn) => Effect.provideService(program, Database, conn))) // reported
    Effect.provideServiceEffect(program, Database, makeConnection)                                // ok

    A quick fix rewrites the expression to Effect.provideServiceEffect(self, Key, acquire) and keeps any later pipe steps: Effect.suspend(() => step(s)).pipe(Effect.flatMap((meta) => Effect.provideService(effect, Key, meta)), Effect.map(f)) becomes Effect.provideServiceEffect(effect, Key, Effect.suspend(() => step(s))).pipe(Effect.map(f)).

    The callback is not reported when it does anything else: when the parameter appears outside the service argument (in the program, in any earlier step of the program, or in the key), when the program or key uses something the callback binds (the name of a named function expression, or a function-expression callback's own this, super, new.target or arguments, plain or as shorthand { arguments }), when the service argument is not the bare parameter, when steps follow provideService, when the acquired value's type is not assignable to the key's service type (for example through a (conn: any) parameter), or when the flatMap result type differs from the provideServiceEffect one (a return-type annotation on the callback or explicit type arguments that widen it, or explicit type arguments on provideService), since code after it may rely on that type. After the fix, the program expression is evaluated once when the expression is built rather than on every run of the callback. The Effect.gen form (const p = yield* acquire; return yield* Effect.provideService(self, Key, p)) is deliberately not reported. On Effect v3, data-first Effect.andThen(acquire, callback) is not reported, since its overloads do not form a dual. The rule supports Effect v3 and v4.

    Piping-flow fixes can now build an expression for a flow prefix with PipingFlowPrefixExpression, including prefixes that end inside a .pipe(...) or pipe(...) call.

  • 50c28e5: Add the forLoopPushToForEach diagnostic (style, off by default; enable it with "forLoopPushToForEach": "suggestion") and quickfix. Inside an Effect generator, a for (const x of iterable) loop whose only statement is acc.push(yield* effect), with acc a const acc = [] declared just before the loop, is reported. The fix replaces it with Effect.forEach. The fix is not offered when the accumulator is mutated after the loop, or when the loop binding or the yielded expression contains a yield of the generator. The callback is passed directly only when it is a plain single-parameter function applied to the loop variable, whether as f(x), pipe(x, f) or x.pipe(f); otherwise an arrow is kept.

    // before
    const results = []
    for (const item of items) {
      results.push(yield* processItem(item))
    }
    // after
    const results = yield* Effect.forEach(items, processItem)

Patch Changes

  • 75a36b2: Update the TypeScript next tag to typescript@next, which ships typescript-go commit 6bdcb54d23f41bc7098c1f3488ac599c75b852ca, update the TypeScript beta tag to typescript@beta, and update the TypeScript latest tag to typescript@latest. Refresh the Oxlint configuration schema from the selected package.

  • 9ada5da: manualMetricTapToTrack now decides more precisely whether a function-expression callback can become an arrow mapper. It looks for the callback's own this, super, new.target, arguments and name the way the compiler resolves them, through the new typeparser helper UsesFunctionOwnBindings, which flatMapProvideServiceToProvideServiceEffect now uses too.

    The rule now reports callbacks it used to skip, since none of these read a binding of the callback:

    Effect.tap(function(size) { return Metric.update(responseSize, size + sizes.arguments) })       // a property named `arguments`
    Effect.tap(function(size) { return Metric.update(responseSize, size + import.meta.url.length) }) // `import.meta`
    Effect.tap(function(size) {                                                                     // a class that uses its own `this` and `arguments`
      return Metric.update(responseSize, size + new (class { readonly n = this; m() { return arguments.length } })().m())
    })

    It no longer reports a named callback that reads its own name through a shorthand property, which the fix would have left unbound:

    Effect.tap(function record(size) { return Metric.update(responseSize, size + Object.keys({ record }).length) })

    Class expressions are still skipped when their extends clause, a computed member name or a member decorator reads the callback's bindings.

... (truncated)

Commits

Updates @vitest/coverage-istanbul from 5.1.0 to 5.1.1

Release notes

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

v5.1.1

   🚀 Features

   🐞 Bug Fixes

... (truncated)

Commits

Updates vite-plus from 1.6.0 to 1.7.0

Release notes

Sourced from vite-plus's releases.

vite-plus v1.7.0

Vite+ 1.7.0 runs type-aware linting and type checking on tsrs, a Rust port of the TypeScript 7 compiler, gives @voidzero-dev/vite-plus-core a version that encodes the bundled Vite version (8.3.8000 for Vite 8.3.8) so compatible vite plugins pass peer checks, and adds vp check --fix-dangerously.

Features

  • Type-aware linting and type checking in vp lint and vp check use tsrs, a Rust port of the TypeScript 7 compiler, through its tsrs-lint executable. Commands and configuration stay the same, and tsrs installs with vite-plus (docs) (#3352), by @​fengmk2:
    • tsrs targets TypeScript 7.1.0-beta, so type-check diagnostics can change.
    • With trustPolicy: no-downgrade in pnpm-workspace.yaml, pnpm rejects the bundled tsrs release (upstream issue). vp migrate adds tsrs@7.1.0-beta.tsrs2 to trustPolicyExclude, so run it if this policy blocks the upgrade.
    • Benchmark with the same CLI and oxlint@1.93.0 on an Apple M4 Max, previous backend (oxlint-tsgolint@7.0.2007) → tsrs. Time is the median of 10 runs, and peak memory the median of 5 runs:
      Project Workload Time Peak memory
      Vite+ Type-aware rules 1.51 → 1.23 s (-18%) 1.21 → 0.58 GiB (-52%)
      Vite+ Type-aware rules + type check 1.89 → 1.38 s (-27%) 1.28 → 0.65 GiB (-49%)
      Vite+ Full vp check 2.09 → 1.70 s (-19%) 1.46 → 0.70 GiB (-52%)
      vinext Type-aware rules 2.73 → 1.66 s (-39%) 3.61 → 1.73 GiB (-52%)
      vinext Type-aware rules + type check 3.41 → 1.73 s (-49%) 3.72 → 1.82 GiB (-51%)
      vinext Full vp check 4.73 → 2.20 s (-53%) 5.09 → 1.97 GiB (-61%)
  • @voidzero-dev/vite-plus-core has a version that encodes the bundled Vite version: 8.3.8000 for Vite 8.3.8 in this release. Projects alias vite to this package, so plugins whose vite peer range includes the bundled Vite, such as @vitejs/plugin-react with ^8.0.0, now pass peer checks. npm no longer prints ERESOLVE overriding peer dependency warnings, and npm and Bun projects that declare only vite-plus install one copy of Vite for Vitest and Vite+, about 20 MiB less in node_modules on macOS arm64 (#3317), by @​fengmk2:
    • On pnpm 10.2.0 and later, vp migrate removes the broad vite rule from peerDependencyRules. A plugin whose vite peer range excludes the bundled Vite then reports a peer warning, and with strictPeerDependencies the install fails. Update that plugin, or allow its range for that plugin only (migration rules).
    • vite-plus and the core no longer share a version number. If you update them by hand or with a dependency bot, read the alias with npm view vite-plus@1.7.0 dependencies.vite, or run vp migrate to update both (docs).
  • vp check --fix-dangerously formats files and applies all lint fixes, including dangerous fixes and suggestions. It does not need --fix, and it works with --no-fmt and --continue-on-error. Review the changes before you commit them, because dangerous fixes can change program behavior (docs) (#3413), by @​chbaefront.
  • vp create with a third-party create-xxx template asks about agent instructions, editor configs, Git, and commit hooks after the template's own CLI finishes, and checks what that CLI generated: it offers to append to an existing agent file, merges existing editor configs, and asks about Git only when the template did not create a repository. When the generated standalone project already depends on vite-plus, vp create keeps the template's choices, such as ESLint or its vite-plus version, and skips the migration. Set VP_FORCE_MIGRATE=1 to run it (#3424, #3435), by @​liangmiQwQ.
  • Upgrade the bundled tools (#3436, #3440, #3452, #3463, #3470), by @​voidzero-guard[bot] and @​fengmk2:
    Tool Version What changes for you
    Vite 8.3.7 → 8.3.8 Rejects CSS entry points when build.cssCodeSplit is false, and imports Sass once instead of once per file
    Rolldown 1.2.18 → 1.2.19 The linux-x64-gnu binding runs on older CPUs
    oxc-node 1.0.1 → 1.0.2 vpx runs CommonJS TypeScript files the way tsc compiles them
    Oxlint 1.93.0 → 1.94.0 Fixes that can change behavior are now suggestions, applied only by vp check --fix-dangerously
    Oxfmt 0.78.0 → 0.79.0 Uses Prettier 3.10.1, so formatting can change
    lint-staged 17.6.0 → 17.6.1 vp staged warns about hidden partial changes only when it restores them
    • If your CI runs vp check, run vp check --fix --continue-on-error after you upgrade: the new Oxlint, Oxfmt, and tsrs can flag code that passed before.

Fixes & Enhancements

  • vp upgrade no longer deletes a version directory that it did not create when an installation fails, so vp upgrade --rollback still finds the previous version after a failed reinstall. vp upgrade, vp upgrade --rollback, and installer setup wait for each other, so two upgrades that run at the same time can no longer leave current pointing to a missing directory. vp upgrade also repairs an active version whose vp binary is missing (#3412), by @​jong-kyung and @​fengmk2.
  • An empty VP_NODE_SKIP_SIGNATURE_VERIFY, VP_NODE_DIST_MIRROR, or npm_config_registry (in either letter case) counts as unset, as in pnpm. Before, VP_NODE_SKIP_SIGNATURE_VERIFY="" turned off PGP verification of Node.js downloads, and an empty mirror or registry failed with relative URL without a base (#3444), by @​jong-kyung.
  • With a token for the default npm registry in .npmrc, the package-manager shims again use cached dist-tags for a latest default and fall back to the cache offline, instead of waiting on the registry at each call and failing when it cannot be reached. Other authenticated registries still skip the cache (#3457), by @​liangmiQwQ.
  • vp pack uses pack.envPrefix from vite.config.ts. Before, the default prefixes VITE_PACK_ and TSDOWN_ always replaced it, so variables under the configured prefix were not inlined and variables under the default prefixes were. The --env-prefix flag still takes precedence (#3454), by @​jong-kyung.
  • vp migrate --full on a project that the first migration left on ESLint and Prettier no longer loses their settings. When vite.config.ts holds only the default lint and fmt blocks that vp migrate added, the converted settings replace them. When those blocks have your own settings, the converted .oxlintrc.json or Prettier stays in place with a warning (#3464), by @​jong-kyung.
  • vp migrate writes npmPreapprovedPackages to .yarnrc.yml only for Yarn 4.10.0 and later. Older Yarn versions do not know this key and refused to run, so migrated Yarn 2 and 3 projects, and Yarn 4.0 to 4.9 projects whose Yarn upgrade failed, could not install (#3443), by @​jong-kyung.
  • vp migrate merges the duplicate vite-plus imports that it creates when it rewrites vite imports, so import/no-duplicates no longer reports them. Comments, side-effect imports, and code between the imports stay in place (#3439), by @​voidzero-bot[bot] and @​fengmk2.
  • A second vp migrate run keeps oxlint in the dependencies of a package that publishes an Oxlint plugin, as the first run does (#3462), by @​jong-kyung.
  • vp migrate warns when the root or a workspace package has turbo.json, turbo.jsonc, or a turbo dependency, because vp run does not read Turborepo configuration. The warning links to the task and cache guides for manual migration (#3300), by @​voidzero-bot[bot] and @​fengmk2.
  • When vp create adds a third-party template to a monorepo, it rewrites the new package's vite imports to vite-plus, so vp check no longer reports vite-plus/prefer-vite-plus-imports errors there (#3282), by @​voidzero-bot[bot] and @​fengmk2.
  • New monorepos from vp create reference their dependency catalog entries with catalog: and contain no unused entries, and the TypeScript and @types/node catalog versions match the generated packages (#3393), by @​d4rshnn.
  • vp create works in projects pinned to Yarn 1.x: it runs templates with npx --yes, as vp dlx does, because Yarn Classic has no yarn dlx (#3468), by @​jong-kyung.
  • vp env exec --node and vp env pin accept lts/*, lts/<codename>, and lts/-n, as vp env use does. vp env pin lts/* writes the resolved exact version (#3437), by @​jong-kyung.
  • Ctrl+C or SIGTERM during a spinner in vp create and vp migrate ends the command by that signal, so the shell reports 130 or 143 instead of 0, as for the native spinners since 1.6.0. Escape no longer ends the command while a spinner is visible (#3432), by @​jong-kyung.
  • The Vitest resolver that defineConfig adds declares a resolveId filter, so Rolldown builds skip it without a call into JavaScript for imports other than vitest, vitest/*, @vitest/*, and vite-plus/test. A synthetic build with 40,000 resolveId calls and no other work took 1.4 s instead of 1.9 s (#3434), by @​jasonkuhrt.

... (truncated)

Commits
  • a3f54d7 release: v1.7.0 (#3471)
  • 77feb44 feat(lint): replace tsgolint with tsrs-lint (#3352)
  • 60ab6e5 feat(deps): upgrade upstream dependencies (#3470)
  • eb2b757 fix(migrate): keep converted ESLint and Prettier settings when default blocks...
  • 3302ead fix(migrate): keep a published Oxlint plugin's oxlint dependency on rerun (#3...
  • b6d8400 fix(create): fall back to npx for Yarn Classic templates (#3468)
  • 6e81fa6 fix(create): use monorepo dependency catalogs (#3393)
  • 9fc3597 fix(pack): respect envPrefix from the config file (#3454)
  • 4dc066a feat: align the core version with the bundled Vite version (#3317)
  • a25ca09 fix(create): rewrite imports when adding a package to a monorepo (#3282)
  • Additional commits viewable in compare view

Updates vitest from 5.1.0 to 5.1.1

Release notes

Sourced from vitest's releases.

v5.1.1

   🚀 Features

   🐞 Bug Fixes

... (truncated)

Commits

@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Nov 19, 2026
@changeset-bot

changeset-bot Bot commented Nov 19, 2026 •

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 0a37311

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@socket-security

socket-security Bot commented Nov 19, 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
Updated@​voidzero-dev/​vite-plus-core@​1.6.0 ⏵ 8.3.80009810077 +199100
Updated@​effect/​tsgo@​0.69.0 ⏵ 0.73.2100 +1100100 +197100
Updatedvite-plus@​1.6.0 ⏵ 1.7.098100100100100

View full report

@dependabot dependabot Bot changed the title chore: Bump the toolchain group with 4 updates chore: Bump the toolchain group across 1 directory with 4 updates Nov 20, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/toolchain-820c5deaab branch from b1016df to 841987d Compare November 20, 2026 01:14
dependabot Bot and others added 2 commits November 20, 2026 21:26
Bumps the toolchain group with 4 updates in the / directory: [@effect/tsgo](https://github.com/Effect-TS/tsgo/tree/HEAD/_packages/tsgo), [@vitest/coverage-istanbul](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-istanbul), [vite-plus](https://github.com/voidzero-dev/vite-plus/tree/HEAD/packages/cli) and [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest).


Updates `@effect/tsgo` from 0.69.0 to 0.70.0
- [Release notes](https://github.com/Effect-TS/tsgo/releases)
- [Changelog](https://github.com/Effect-TS/tsgo/blob/main/_packages/tsgo/CHANGELOG.md)
- [Commits](https://github.com/Effect-TS/tsgo/commits/@effect/tsgo@0.70.0/_packages/tsgo)

Updates `@vitest/coverage-istanbul` from 5.1.0 to 5.1.1
- [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/v5.1.1/packages/coverage-istanbul)

Updates `vite-plus` from 1.6.0 to 1.7.0
- [Release notes](https://github.com/voidzero-dev/vite-plus/releases)
- [Commits](https://github.com/voidzero-dev/vite-plus/commits/v1.7.0/packages/cli)

Updates `vitest` from 5.1.0 to 5.1.1
- [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/v5.1.1/packages/vitest)

---
updated-dependencies:
- dependency-name: "@effect/tsgo"
  dependency-version: 0.70.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: toolchain
- dependency-name: "@vitest/coverage-istanbul"
  dependency-version: 5.1.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: toolchain
- dependency-name: vite-plus
  dependency-version: 1.7.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: toolchain
- dependency-name: vitest
  dependency-version: 5.1.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: toolchain
...

Signed-off-by: dependabot[bot] <support@github.com>
- vite, vitest and @vitest/coverage-istanbul to what vite-plus 1.7.0
  depends on (vite-plus-core 8.3.8000, vitest 5.1.0); `vite` no longer
  equals the vite-plus version. `vp migrate` also pins `vite` / `vitest`
  through overrides and gives the examples `vitest` as a devDependency
  (for @effect/vitest's peer).
- @effect/tsgo 0.73.2, which supports tsrs (vite-plus 1.7.0's type-aware
  linter); `prepare` now patches tsrs too.
- @effect/tsgo 0.73.2 rejects the deprecated `preferSchemaOverJson`
  severity: use `globalJsonInEffect`, its in-Effect replacement.
- Lint with `typeCheck: false`: tsrs's type check reports the Effect
  language service's warnings as errors. `vp run check` stays the gate.
- Its new `flat-map-map-to-zip-with` finding: Effect.zipWith in the
  conformance evaluation. Three files re-formatted by the new oxfmt.
- `pack` keeps resolving dependency subpaths (tsdown <0.23 behaviour).
- Drop the peerDependencyRules the aliased `vite` needed.
- Devcontainer image to vite-plus 1.7.0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Y5G6PJKoiZuM4rdHsaVhdw
@thomasfosterau
thomasfosterau force-pushed the dependabot/npm_and_yarn/toolchain-820c5deaab branch from 841987d to 0a37311 Compare November 20, 2026 21:46

This branch has not been deployed

No deployments
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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants