fix(deps): update all dependencies by renovate[bot] · Pull Request #31 · ProverCoderAI/effect-template

renovate · 2026-02-19T08:15:38Z

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Type	Update
@biomejs/biome (source)	`^2.4.0` → `^2.6.6`	devDependencies	minor
@changesets/changelog-github (source)	`^0.5.2` → `^1.0.1`	devDependencies	major
@changesets/cli (source)	`^2.29.8` → `^3.0.3`	devDependencies	major
@effect/cli (source)	`^0.73.2` → `^0.77.2`	dependencies	minor
@effect/cluster (source)	`^0.56.4` → `^0.60.2`	dependencies	minor
@effect/experimental (source)	`^0.58.0` → `^0.61.1`	dependencies	minor
@effect/platform (source)	`^0.94.5` → `^0.97.2`	dependencies	minor
@effect/platform-node (source)	`^0.104.1` → `^4.1.2`	dependencies	major
@effect/printer (source)	`^0.47.0` → `^0.51.0`	dependencies	minor
@effect/printer-ansi (source)	`^0.47.0` → `^0.51.0`	dependencies	minor
@effect/rpc (source)	`^0.73.1` → `^0.76.2`	dependencies	minor
@effect/sql (source)	`^0.49.0` → `^0.52.1`	dependencies	minor
@effect/typeclass (source)	`^0.38.0` → `^0.41.0`	dependencies	minor
@effect/vitest (source)	`^0.27.0` → `^4.1.2`	devDependencies	major
@effect/workflow (source)	`^0.16.0` → `^0.19.1`	dependencies	minor
@eslint-community/eslint-plugin-eslint-comments	`^4.6.0` → `^4.8.1`	devDependencies	minor
@eslint/compat (source)	`2.0.2` → `2.1.1`	devDependencies	minor
@eslint/eslintrc	`3.3.3` → `3.3.7`	devDependencies	patch
@prover-coder-ai/eslint-plugin-suggest-members	`^0.0.25` → `^0.0.26`	devDependencies	patch
@types/node (source)	`^24.10.13` → `^26.6.6`	devDependencies	major
@typescript-eslint/eslint-plugin (source)	`^8.55.0` → `^8.72.2`	devDependencies	minor
@typescript-eslint/parser (source)	`^8.55.0` → `^8.72.2`	devDependencies	minor
@vitest/coverage-v8 (source)	`^4.0.18` → `^5.1.0`	devDependencies	major
@vitest/eslint-plugin	`^1.6.9` → `^1.6.28`	devDependencies	patch
actions/checkout	`v6` → `v7`	action	major
actions/setup-node	`v6` → `v7`	action	major
actions/upload-artifact	`v6` → `v7`	action	major
effect (source)	`^3.19.17` → `^4.1.2`	dependencies	major
eslint (source)	`^10.0.0` → `^10.14.0`	devDependencies	minor
eslint-import-resolver-typescript	`^4.4.4` → `^4.4.5`	devDependencies	patch
eslint-plugin-simple-import-sort	`^12.1.1` → `^14.0.0`	devDependencies	major
eslint-plugin-sonarjs (source)	`^3.0.7` → `^4.2.2`	devDependencies	major
eslint-plugin-sort-destructure-keys	`^2.0.0` → `^3.0.0`	devDependencies	major
eslint-plugin-unicorn	`^63.0.0` → `^79.0.0`	devDependencies	major
globals	`^17.3.0` → `^17.14.0`	devDependencies	minor
jscpd (source)	`^4.0.8` → `^5.4.3`	devDependencies	major
node	`24.13.1` → `26.13.0`	uses-with	major
pnpm (source)	`10.29.3` → `12.18.0`	packageManager	major
pnpm/action-setup	`v4` → `v6`	action	major
pnpm/action-setup	`v3` → `v6`	action	major
ts-morph	`^27.0.2` → `^28.0.0`	dependencies	major
typescript (source)	`^5.9.3` → `^7.0.2`	devDependencies	major
typescript-eslint (source)	`^8.55.0` → `^8.72.2`	devDependencies	minor
vite (source)	`^7.3.1` → `^8.3.7`	devDependencies	major
vitest (source)	`^4.0.18` → `^5.1.0`	devDependencies	major

cc @skulidropek

Release Notes

biomejs/biome (@biomejs/biome)

`v2.6.6`

Compare Source

Patch Changes

#12887 da0422e Thanks @dyc3! - Added the new nursery rule noArrayMethodsOnArguments. It reports calls to array methods on the arguments object, which isn't an array, so these calls throw a TypeError when the code runs.
```
function sum() {
  return arguments.reduce((total, value) => total + value, 0);
}
```
#12877 cd9e10f Thanks @dyc3! - Added the nursery rule noConstantComparisons, which reports && and || conditions that can never be true, are always true, or contain a check with no effect.
```
if (statusCode <= 400 && statusCode > 500) {}
```
#12876 a7c9586 Thanks @dyc3! - Added the nursery rule noErasingOperation, which disallows operations with 0 that always result in zero: multiplying by 0, a bitwise AND with 0, and dividing 0 by a number. The other value in these operations has no effect on the result, which usually means the code has a mistake.
```
const total = price * 0;
```
#12841 e954f55 Thanks @dyc3! - Added the nursery rule noNegatedArrayPredicate, which reports negated calls to Array#some() and Array#every() and suggests moving the negation into the callback function.
```
// Invalid: use `array.every((item) => !isUnicorn(item))` instead.
const isMissing = !array.some((item) => isUnicorn(item));
```
#12888 15039f7 Thanks @dyc3! - Added the new nursery rule noNumberArgumentOutOfRange, which reports number literal arguments of toString(), toFixed(), toExponential() and toPrecision() that are outside the range the method accepts. These calls throw a RangeError at runtime.
```
value.toString(64);
```
#12889 1cd7520 Thanks @dyc3! - Added the nursery rule noSharedBranchCode, which reports code that is repeated at the start or end of every branch of an if statement. That code runs no matter which branch is taken, so it can be moved before or after the if statement.
```
if (condition) {
  doSomething();
  cleanup();
} else {
  doSomethingElse();
  cleanup();
}
```
#12842 d47fcfd Thanks @dyc3! - Added the new nursery rule noSubtractionComparison, which reports subtracting two values only to compare the difference with 0, and suggests comparing the values directly.
```
if (a - b > 0) {}
```
#12866 7c1cd5f Thanks @dyc3! - Added the nursery rule noSvelteIgnoredUnsubscribe, which reports calls to a store's subscribe() method when the returned function is ignored. Without that function, the subscription can never be stopped, which causes a memory leak.
```
<script>
  import { count } from "./stores.js";

  count.subscribe((value) => console.log(value));
</script>
```
#12890 6b73fcf Thanks @dyc3! - Added the new nursery rule noUninvokedArrayCallback, which reports array methods such as map() and forEach() called with a callback on an array that only has empty slots. The callback never runs in this case.
```
const list = new Array(5).map(() => createElement());
```
#12886 3bb18d8 Thanks @dyc3! - Added the nursery rule useNextScriptForGoogleAnalytics, which reports <script> elements that load Google Analytics or Google Tag Manager. Use the GoogleAnalytics and GoogleTagManager components from @next/third-parties/google instead, which load these scripts after the page becomes interactive.
```
<script async src="https://www.googletagmanager.com/gtag/js?id=G-XYZ" />
```
The rule belongs to the next domain.
#12309 0538e30 Thanks @dyc3! - Added the new nursery rule usePackageJsonCpu, which reports package.json files that have no cpu field. The cpu field lists the processor types that the package supports.

The following package.json file satisfies the rule:
```
{
  "name": "my-package",
  "version": "1.0.0",
  "cpu": ["x64", "arm64"]
}
```
#12310 191111d Thanks @dyc3! - Added the nursery rule usePackageJsonEngines, which reports package.json files that have no engines field.

A package.json passes the rule once it declares the field:
```
{
  "name": "my-package",
  "engines": {
    "node": ">=20"
  }
}
```
#12986 cc929af Thanks @dyc3! - Fixed #12954, where configuring rules in groups with more than 256 rules could enable or disable the wrong rule.
#12931 fe9248e Thanks @dyc3! - Improved the performance of linting. Each lint pass now spends less time stepping over syntax nodes that no enabled rule looks at.
#12969 22d27e8 Thanks @vibbix! - Improved the performance of CSS linting. Rules that compare selectors, such as noDescendingSpecificity and noDuplicateSelectors, now make fewer memory allocations.
#12973 5a06df5 Thanks @vibbix! - Fixed useGenericFontNames reporting font-family inside @font-palette-values. There, font-family names the font families the palette applies to, so it doesn't take a generic family.
```
@font-palette-values --palette {
  font-family: Bixa;
  override-colors: 0 red;
}
```
#12930 ce71284 Thanks @dyc3! - Fixed #12073: useExhaustiveSwitchCases now reports non-exhaustive switches over values read from for...of loops over Array.prototype.entries(), Map, and Set, and over properties of array elements indexed by a number variable.

noMisusedPromises now also reports Promise-returning callbacks passed to array methods such as find and every.
#12983 2987b54 Thanks @ashokram-si! - Fixed #12957: Biome now correctly parses SCSS negative interpolation list items as separate values instead of an invalid subtraction operator.
```
-margin: -#{$s} - #{$s} - #{$s} auto;
+margin: -#{$s} -#{$s} -#{$s} auto;
```

`v2.6.5`

Compare Source

Patch Changes

#12755 bbc4887 Thanks @dyc3! - Added the new nursery rule noArrayForEach, which reports forEach() calls that can be written as for...of loops. Values known not to be arrays, such as a Map or a Set, are ignored.
```
array.forEach((element) => {
	bar(element);
});
```
#12777 ba692e4 Thanks @dyc3! - Added the new nursery rule noAwaitInPromiseMethods, which reports await inside the array passed to Promise.all(), Promise.allSettled(), Promise.any(), or Promise.race(). The await pauses the code before the method is called, so the promises no longer run at the same time.
```
Promise.all([await promise, anotherPromise]);
```
#12765 af84fb4 Thanks @dyc3! - Added the new nursery rule noChainedComparison, which reports comparisons chained like a < b < c or a === b === c. JavaScript compares a with b first, and then compares the resulting true or false with c, so 3 > 2 > 1 is false.
```
if (a < b < c) {}
```
#12547 0a2073d Thanks @dyc3! - Added the nursery rule noDynamicDelete, which disallows using delete with a property name that is computed at runtime. Fixed property names written as string or number literals are allowed.
```
delete container[name];
```
#12481 ed7adc2 Thanks @dyc3! - Added the nursery rule noLateEventControl, which reports calls to preventDefault(), stopPropagation(), and stopImmediatePropagation() that run after the browser has finished handling the event, where they have no effect.
```
element.addEventListener("click", async (event) => {
  await save();
  event.preventDefault();
});
```
#12795 179666d Thanks @dyc3! - Added the nursery rule noMapSpread, which disallows spreading objects or arrays in the values returned by map() and flatMap() callbacks. Each spread copies a whole object or array for every item, which is slow for large arrays. Its unsafe fix replaces an object that starts with a spread with Object.assign().
```
const users = getUsers();
const rows = users.map((user) => ({ ...user, role: getRole(user) }));
```
#12793 d9a99fd Thanks @dyc3! - Added the nursery rule noMismatchedMapKey, which reports get() and set() calls that use a different key than the has() check before them. Checking one key and then using another is usually a copy-paste mistake.
```
if (map.has(key)) {
  map.get(otherKey); // reported
}
```
#12342 1db7c0d Thanks @vibbix! - Added the nursery rule noMissingScssInterpolation, which disallows Sass variables and function calls in custom property values without #{} interpolation. Sass copies these values into the CSS unchanged, so the browser receives $gap or math.div(8px, 2) instead of their results. Its unsafe fix wraps variables in #{}.
```
:root {
  --gap: $gap;
  --half: math.div(8px, 2);
}
```
#12792 de86b37 Thanks @dyc3! - Added the nursery rule noMissingThrow, which reports errors that are created with new but never thrown. Its unsafe fix adds the missing throw keyword.
```
function check(value) {
  if (!value) {
    new Error("Missing value");
  }
}
```
#12790 c23e4c3 Thanks @dyc3! - Added the new nursery rule noObjectLiteralComparison, which reports comparisons with an empty object {} or an empty array []. These comparisons never check whether a value is empty, because objects and arrays are compared by reference.
```
if (value === {}) {}
```
#12450 793f07d Thanks @dyc3! - Added the new nursery rule noPlaywrightUnsafeReferences, which reports functions passed to page.evaluate() or page.addInitScript() that use variables declared outside of them. Playwright runs these functions in the browser page, where those variables don't exist.
```
const x = 7;
await page.evaluate(() => x * 2); // reported: `x` must be passed as an argument
```
#12388 a0160a4 Thanks @vibbix! - Added the nursery rule noPseudoElementInFunctionalPseudoClass, which disallows pseudo-elements inside :is(), :where(), :not() and :has(). Browsers drop these selectors, so the styles never apply to the pseudo-element.
```
.card:is(::before, ::after) {
  content: "";
}
```
#12779 bc1befb Thanks @dyc3! - Added the new nursery rule noSinglePromiseInPromiseMethods, which reports an array with a single element passed to Promise.all(), Promise.any(), or Promise.race(). The rule offers a fix that awaits the value directly or uses Promise.resolve().
```
const result = await Promise.all([promise]);
```
#12241 d96de1d Thanks @dyc3! - Added the nursery rule noSvelteBindValueOnCheckableInputs, which reports bind:value on checkbox and radio inputs in Svelte files. Users change whether these inputs are checked, not their value, so bind:value does not track their choice.
```
<input type="checkbox" bind:value={accepted} />
```
#12764 e166d08 Thanks @dyc3! - Added the new nursery rule noSyncMethods, which reports calls to functions whose names end with Sync, such as fs.readFileSync(). These calls block the program until they finish. The allowAtRootLevel option allows them outside of functions, and the ignore option allows specific function names.
```
const contents = fs.readFileSync("data.txt");
```
#12515 c0a4174 Thanks @dyc3! - Added the nursery rule noTanstackQueryVoidQueryFn, which disallows TanStack Query functions that don't return any data. TanStack Query doesn't accept undefined as the data of a query, so the query fails with an error.
```
import { useQuery } from "@tanstack/react-query";

useQuery({
    queryKey: ["todos"],
    queryFn: async () => {
        await fetch("/api/todos");
    },
});
```
The rule belongs to the tanstackQuery and types domains.
#12482 1e6e407 Thanks @dyc3! - Added the nursery rule noUnnecessaryStringTrim, which reports trim() calls before startsWith() or endsWith() when only one side of the string matters. Use trimStart() or trimEnd() instead.
```
value.trim().startsWith("-");
```
#12772 a108773 Thanks @dyc3! - Added the nursery rule noUselessAwait, which reports await on values that are never promises, such as literals, arrays, and the results of comparisons.
```
await [fetchUser(), fetchPosts()];
```
#12783 d0931b0 Thanks @dyc3! - Added the new nursery rule noUselessLengthCheck, which reports array length checks that don't change the result: a check that the array is empty next to every(), a check that it isn't empty next to some(), or a check that it isn't empty around a for...of loop over the same array.
```
if (array.length > 0 && array.some(Boolean)) {}
```
#12488 93e0e73 Thanks @dyc3! - Added the new nursery rule noUselessTypeAssertion, which reports type assertions that don't change the type of an expression, such as a non-null assertion on a value that can't be null or undefined.
```
function double(value: number): number {
  return value! * 2;
}
```
#12632 0e197b4 Thanks @dyc3! - Added the nursery rule noVueChildContent, which disallows content inside elements that use v-html or v-text. These directives replace the content of their element, so Vue discards anything written there.
```
<template>
  <div v-html="html">Loading...</div>
</template>
```
#12616 cb7b888 Thanks @dyc3! - Added the new nursery rule noVueDeprecatedConfigKeyCodes, which reports uses of Vue.config.keyCodes. Vue 3 removed this option, so custom key names defined with it no longer work.
```
Vue.config.keyCodes = { f1: 112 };
```
#12568 59f3a42 Thanks @dyc3! - Added the nursery rule noVueDeprecatedDestroyedLifecycle, which reports the beforeDestroy and destroyed lifecycle hooks in Vue components. Vue 3 renamed them to beforeUnmount and unmounted, and no longer calls hooks with the old names.
```
<script>
export default {
  destroyed() {},
};
</script>
```
#12654 bcb1e0f Thanks @dyc3! - Added the nursery rule noVueDeprecatedEventsApi, which reports calls to the $on, $off, and $once instance methods in Vue components. Vue 3 removed these methods, so calling them throws an error.
```
<script>
export default {
  mounted() {
    this.$on("start", handler); // reported
  },
};
</script>
```
#12590 b9872ef Thanks @dyc3! - Added the nursery rule noVueDeprecatedFunctionalTemplate, which reports the functional attribute on the <template> of a Vue component. Vue 3 no longer supports this attribute.
```
<template functional>
  <div>{{ props.message }}</div>
</template>
```
#12552 b71b705 Thanks @dyc3! - Added the nursery rule noVueDeprecatedHtmlElementIs, which disallows the is attribute on HTML elements in Vue templates. Vue 3 no longer renders a component in place of these elements, unless the value starts with vue:.
```
<template>
  <tr is="my-row"></tr>
</template>
```
#12553 4a613e1 Thanks @dyc3! - Added the nursery rule noVueDeprecatedInlineTemplate, which disallows the inline-template attribute on Vue components. Vue 3 removed this feature, so the content between the component's tags is no longer used as its template.
```
<template>
  <my-component inline-template>
    <div>{{ message }}</div>
  </my-component>
</template>
```
#12617 0e9ca5b Thanks @dyc3! - Added the nursery rule noVueDeprecatedModelDefinition, which reports the model option in Vue components. Vue 3 ignores this option, so v-model on the component always uses the modelValue prop and the update:modelValue event.
```
<script>
export default {
  model: {
    prop: "checked",
    event: "change",
  },
};
</script>
```
#12604 e998921 Thanks @dyc3! - Added the nursery rule noVueDeprecatedPropsDefaultThis, which reports this inside the function that computes the default value of a Vue prop. Vue doesn't give this function access to the component, so this doesn't point to it. Read other pr

[!IMPORTANT]
✂ PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

Branch creation
- At any time (no schedule defined)
Automerge
- At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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.

coderabbitai · 2026-05-14T13:49:37Z

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

Source mode: Auto
Repository: Unavailable
Branch: Unavailable
File: No configuration file from this repository applied
Commit: Unavailable
Layers: Organization UI
Review profile: CHILL
Plan: Advanced
Run ID: ba1ceac0-45b4-474c-ab2b-192f1dffa61c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

Trigger review

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Last reviewed commit: 713885b
Latest commit, not reviewed: 246bce4

Use the following commands to manage reviews:

@coderabbitai resume to resume automatic reviews.
@coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

▶️ Resume reviews
🔍 Trigger review

Walkthrough

Bumps pnpm to 11.1.3 at root and app, upgrades Changesets and many app deps/devDeps, and updates GitHub Actions versions: pnpm/action-setup → v6, Node runtime → 24.15.0, and actions/upload-artifact → v7.

Changes

Dependency and Action Upgrades

Layer / File(s)	Summary
Root package manager and Changesets tooling `package.json`	Root `package.json` updated to `packageManager: "pnpm@11.1.3"` and Changesets devDependencies (`@changesets/changelog-github`, `@changesets/cli`) bumped.
App package manager and dependency upgrades `packages/app/package.json`	`packages/app` `packageManager` set to `pnpm@11.1.3`; multiple runtime `dependencies` and `devDependencies` (including `@effect/*`, `effect`, `ts-morph`, tooling, TypeScript, Vite/Vitest, linters) have version bumps.
GitHub Actions and workflow configuration `.github/actions/setup/action.yml`, `.github/workflows/checking-dependencies.yml`, `.github/workflows/snapshot.yml`	Composite action/workflows updated: `pnpm/action-setup` bumped to `v6`, `actions/setup-node` node-version changed to `24.15.0`, and `actions/upload-artifact` bumped to `v7`.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related issues

Dependency Dashboard openapi-effect#1 — Matches Renovate-style dependency and workflow version bumps (pnpm and action versions).
Dependency Dashboard eslint-plugin-suggest-members#2 — Overlaps CI and Changesets dependency/version updates present in this PR.
Dependency Dashboard #10 — Similar CI/action and package metadata updates (pnpm, actions, packageManager).
Dependency Dashboard context-doc#5 — Contains comparable dependency/version adjustments across workflows and manifests.
Dependency Dashboard dist-deps-prune#2 — Related updates to GitHub Action versions and package.json dependency entries.
Dependency Dashboard effect-eslint-template#6 — Mirrors pnpm/action-setup and pnpm packageManager version bumps seen here.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly identifies the pull request as a dependency update, which matches the primary changes across packages, tooling, and CI actions.
Description check	✅ Passed	The description directly documents the Renovate-generated dependency, package manager, CI action, and runtime version updates.

Finishing Touches

Generate docstrings

Create stacked PR
Commit on current branch

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch renovate/all

Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

_{🐰 A patch of pins and versions new,
I nibbled bumps and pushed them through.
Workflows hum and artifacts sing,
PNPM hops to a brighter spring.
— Rabbit with a CI carrot 🥕}

coderabbitai

Actionable comments posted: 4

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/actions/setup/action.yml:
- Line 13: The action uses pnpm/action-setup@v6 but the custom action default
still sets node-version: 20.16.0 which is incompatible; update the default
node-version in action.yml to Node 24 (>=24.0.0, e.g., 24.15.0 to match
checking-dependencies.yml) so the action runs on the required runtime, and after
changing the default verify pnpm selection behavior (packageManager in
package.json / pnpm@11.1.2) because v6 has a bug that may ignore
packageManager—if necessary pin the pnpm version explicitly or add configuration
to enforce packageManager to ensure the expected pnpm version is used.

In @.github/workflows/checking-dependencies.yml:
- Line 15: The workflow uses pnpm/action-setup@v6 but package.json declares
packageManager: pnpm@11.1.2, causing a mismatch; either align the workflow or
package.json: update package.json's packageManager to "pnpm@11.1.1" to match the
action's default, or explicitly configure the action in
.github/workflows/checking-dependencies.yml (pnpm/action-setup) with a
compatible with.version value (e.g., 11.1.1) until 11.1.2 is released, or remove
the explicit version so the action auto-detects from package.json and surfaces
the proper error if the version is unavailable.

In `@package.json`:
- Line 6: Update package.json to remove deprecated pnpm v10 fields and adopt
pnpm v11 format: replace any ignoredBuiltDependencies and onlyBuiltDependencies
entries with the new allowBuilds configuration (mapping allowed package patterns
or booleans accordingly) and set the engines.node field to ">=22" (or "22.x" per
project policy) so Node.js requirement is explicit for pnpm 11; also keep
packageManager set to "pnpm@11.1.2" and run the pnpm v10→v11 codemod (pnpx
codemod run pnpm-v10-to-v11) to ensure any other migration changes are applied.

In `@packages/app/package.json`:
- Line 71: Add an "engines" entry to packages/app/package.json to require
Node.js >=20.19.0 so ESLint 10.3.0 runs correctly; locate the existing "eslint":
"^10.3.0" dependency in package.json and add an "engines" object with "node":
">=20.19.0" to enforce the minimum Node version for contributors and CI.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

Push a commit to this branch (recommended)
Create a new PR with the fixes

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 99f915a6-56ca-42ec-8fc8-02ccf3d20151

📥 Commits

Reviewing files that changed from the base of the PR and between 2b21043 and f9810e9.

⛔ Files ignored due to path filters (1)

pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (5)

.github/actions/setup/action.yml
.github/workflows/checking-dependencies.yml
.github/workflows/snapshot.yml
package.json
packages/app/package.json

coderabbitai · 2026-05-14T13:55:11Z

    steps:
      - uses: actions/checkout@v6
-      - uses: pnpm/action-setup@v4
+      - uses: pnpm/action-setup@v6


⚠️ Potential issue | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🌐 Web query:

pnpm/action-setup v6 release notes

💡 Result:

pnpm/action-setup v6 release notes (from the repo’s official GitHub Releases pages) are available as a series of versioned release entries under the v6 tags. The most recent v6 entry visible in the official releases feed is v6.0.8 (published 2026-05-12), with the following changes: 1) v6.0.8 (2026-05-12) - docs(README): fix cache_dependency_path type (PR #257) [1] - fix: drop patchPnpmEnv so standalone+self-update works on Windows (PR #258) [1] - fix: update pnpm to 11.1.1 (PR #248) [1] 2) v6.0.4 (2026-04-30) - fix: use npm co-located with the action node binary (PR #239) [2] Additional v6 changes are also reflected in the v4...v6 comparison page (including updates to README/examples and caching-related input typing/behavior), which indicates that v6 introduces/updates inputs like cache_dependency_path handling. In that compare view, cache_dependency_path is described as accepting multiple paths delimited by newlines, and the example workflows are updated to use pnpm/action-setup@v6 instead of v4. [3] Notes / where to read the full set of v6 release notes: - Start at the official Releases index for pnpm/action-setup and select the v6.x.y tags. The Releases index is the source of truth for the complete v6 changelog history. [4] If you want, tell me the exact v6 range you care about (e.g., “v6.0.0 through v6.0.8” or “just v6.0.8”), and I’ll summarize only those entries.

Citations:

1: https://github.com/pnpm/action-setup/releases/tag/v6.0.8

2: https://github.com/pnpm/action-setup/releases/tag/v6.0.4

3: pnpm/action-setup@v4...v6

4: https://github.com/pnpm/action-setup/releases

🌐 Web query:

Node.js 24.15.0 release notes

💡 Result:

Node.js 24.15.0 (Krypton, LTS) release notes (published 2026-04-15) list these notable changes: - cli: add --max-heap-size option [1] - cli: add --require-module / --no-require-module [2] - crypto: add raw key formats support to the KeyObject APIs [1] - fs: add throwIfNoEntry option for fs.stat and fs.promises.stat [2] - http2: add http1Options for HTTP/1 fallback configuration [2] - module: mark require(esm) as stable [2] - module: mark module compile cache as stable [2] - net: add setTOS and getTOS to Socket [2] - sqlite: add limits property to DatabaseSync [2] - sqlite: mark as release candidate [2] - src: add C++ support for diagnostics channels [2] - stream: rename Duplex.toWeb type option to readableType [2] - test_runner: add exports option for module mocks [2] - test_runner: expose worker ID for concurrent test execution [2] - test_runner: show interrupted test on SIGINT [2] Primary sources for the above are the official Node.js blog release page and the Node.js v24 changelog section for 24.15.0 [1][2].

Citations:

1: https://nodejs.org/blog/release/v24.15.0

2: https://github.com/nodejs/node/blob/main/doc/changelogs/CHANGELOG_V24.md

🏁 Script executed:

#!/bin/bash # Check all workflow files for consistency in action versions rg -n "pnpm/action-setup@" --type yaml rg -n "node-version:" --type yaml

Repository: ProverCoderAI/effect-template

Length of output: 55

🏁 Script executed:

#!/bin/bash # Check if the workflow file exists ls -la .github/workflows/ 2>/dev/null || echo "Directory not found" # If it exists, read the file if [ -f ".github/workflows/checking-dependencies.yml" ]; then echo "=== File found, reading contents ===" cat -n ".github/workflows/checking-dependencies.yml" else echo "File not found" fi # Also check with fd for any workflow files echo "=== Searching for workflow files ===" fd -e yml -e yaml ".github/workflows/" 2>/dev/null || fd -e yml -e yaml

Repository: ProverCoderAI/effect-template

Length of output: 1412

🏁 Script executed:

#!/bin/bash # Check pnpm version in lock file head -20 pnpm-lock.yaml | grep -i "version\|lockfileVersion" # Also check package.json for pnpm version requirement if any if [ -f "package.json" ]; then grep -i "pnpm" package.json fi # Check if there's a .npmrc or similar config if [ -f ".npmrc" ]; then cat .npmrc fi

Repository: ProverCoderAI/effect-template

Length of output: 745

🌐 Web query:

pnpm 11.1.2 release date and availability

💡 Result:

No evidence found of a pnpm 11.1.2 release as of 2026-05-14. The latest releases are v11.1.1 (published around 2026-05-12 [1]) and v11.1.0 (published 2026-05-11 [2][3][4]). Official GitHub releases page lists recent tags up to May 12 but no 11.1.2 [3]. npm registry tracks these releases [4], and no sources mention 11.1.2. It is not yet released or available.[2][3][1]

Citations:

1: https://newreleases.io/project/github/pnpm/pnpm/release/v11.1.1

2: https://github.com/pnpm/pnpm/releases/tag/v11.1.0

3: https://github.com/pnpm/pnpm/releases

4: https://newreleases.io/project/npm/pnpm/release/11.1.0

🌐 Web query:

pnpm/action-setup configure pnpm version 11.1.2

💡 Result:

To configure pnpm/action-setup to install pnpm 11.1.2, use the action’s with.version input: steps: - uses: pnpm/action-setup@v6 with: version: 11.1.2 The version input is “Version of pnpm to install” and supports exact versions like 11.1.2 (or version ranges/tags). If you omit version, the action can use the packageManager field from your package.json instead.[1] You may optionally specify run_install if you also want the action to run pnpm install for you; otherwise run pnpm install in a later step.[1]

Citations:

1: https://github.com/pnpm/action-setup

Configure pnpm version in pnpm/action-setup to match project requirement.

The workflow uses pnpm/action-setup@v6 which installs pnpm 11.1.1 by default, but the project specifies packageManager: pnpm@11.1.2 in package.json. Since pnpm 11.1.2 does not yet exist, the pnpm install --frozen-lockfile step (line 21) will fail due to version mismatch. Either update package.json to use pnpm 11.1.1, or configure the action with with.version: 11.1.2 once that version is released. Alternatively, the action can auto-detect the version from package.json if no version input is specified (allowing proper error messaging when unavailable).

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.github/workflows/checking-dependencies.yml at line 15, The workflow uses pnpm/action-setup@v6 but package.json declares packageManager: pnpm@11.1.2, causing a mismatch; either align the workflow or package.json: update package.json's packageManager to "pnpm@11.1.1" to match the action's default, or explicitly configure the action in .github/workflows/checking-dependencies.yml (pnpm/action-setup) with a compatible with.version value (e.g., 11.1.1) until 11.1.2 is released, or remove the explicit version so the action auto-detects from package.json and surfaces the proper error if the version is unavailable.

coderabbitai · 2026-05-14T13:55:11Z

  "private": true,
  "description": "Monorepo workspace for effect-template",
-  "packageManager": "pnpm@10.29.3",
+  "packageManager": "pnpm@11.1.2",


⚠️ Potential issue | 🔴 Critical | 🏗️ Heavy lift

🧩 Analysis chain

🌐 Web query:

pnpm 11 release notes breaking changes from pnpm 10

💡 Result:

pnpm 11 introduces several breaking changes from v10, primarily documented in the official migration guide [1] and v11.0.0 release notes [2][3]. Key breaking changes include: Node.js requirement: Now requires Node.js 22 or newer; support for v18-21 dropped. pnpm is pure ESM, and standalone exe needs glibc 2.27+ [3][2][4]. Configuration changes [1]: - No longer reads config from package.json#pnpm; move to pnpm-workspace.yaml. -.npmrc limited to auth/registry; other settings (hoist-pattern, node-linker, etc.) to pnpm-workspace.yaml (camelCase keys). - npm_config_* env vars ignored; use pnpm_config_*. - Deprecated build settings (onlyBuiltDependencies, etc.) removed; use allowBuilds [3][2]. - Package manager settings consolidated to pmOnFail: 'download'|'ignore'|'warn'|'error'. - Renames: allowNonAppliedPatches -> allowUnusedPatches; auditConfig.ignoreCves -> auditConfig.ignoreGhsas. Store upgraded to v11: SQLite index.db replaces JSON files; incompatible with v10 stores (clear or migrate) [3][2][5]. Global installs: Isolated in {pnpmHomeDir}/global/v11/{hash}/ with own package.json/node_modules/pnpm-lock.yaml. pnpm install -g (no args) removed; use pnpm add -g [3][2]. pnpm link changes: No global store resolution; only relative/absolute paths. --global removed (use pnpm add -g.); no-arg pnpm link removed [1][6]. Removed commands: pnpm server; npm passthrough (publish, login, etc.) now native, some like access, edit removed [3][2]. Lockfile: patchedDependencies simplified to selector -> hash; auto-migrated [5]. Script shadowing: Scripts named clean/setup/deploy/rebuild run script, not built-in; use pnpm pm [1]. Security defaults: minimumReleaseAge=1440 (1 day), blockExoticSubdeps=true, strictDepBuilds=true [3][2]. A codemod assists migration: pnpx codemod run pnpm-v10-to-v11 [1]. Full details: https://pnpm.io/migration [1], https://github.com/pnpm/pnpm/releases/tag/v11.0.0 [2], https://pnpm.io/blog/releases/11.0 [3].

Citations:

1: https://pnpm.io/migration

2: https://github.com/pnpm/pnpm/releases/tag/v11.0.0

3: https://pnpm.io/blog/releases/11.0

4: https://github.com/pnpm/pnpm/releases/tag/v11.0.0-rc.0

5: https://github.com/pnpm/pnpm/releases/tag/v11.0.0-alpha.14

6: https://github.com/pnpm/pnpm/releases/tag/v11.0.0-beta.3

🏁 Script executed:

#!/bin/bash # Check if pnpm-lock.yaml has been updated alongside this change git diff HEAD -- pnpm-lock.yaml | head -50

Repository: ProverCoderAI/effect-template

Length of output: 55

🏁 Script executed:

#!/bin/bash # Check if pnpm-lock.yaml exists and what version it specifies if [ -f "pnpm-lock.yaml" ]; then echo "=== pnpm-lock.yaml lockfileVersion ===" head -20 pnpm-lock.yaml | rg "lockfileVersion|name|version" else echo "pnpm-lock.yaml not found" fi # Check if package.json has pnpm config that needs migration echo -e "\n=== package.json pnpm config ===" jq '.pnpm' package.json 2>/dev/null || echo "No pnpm config in package.json" # Check Node.js version requirement echo -e "\n=== Node.js engines requirement ===" jq '.engines' package.json 2>/dev/null || echo "No engines field"

Repository: ProverCoderAI/effect-template

Length of output: 586

🏁 Script executed:

#!/bin/bash # Check git log to see if pnpm-lock.yaml was modified in this change echo "=== Recent git changes to pnpm-lock.yaml ===" git log --oneline -n 10 -- pnpm-lock.yaml 2>/dev/null || echo "No pnpm-lock.yaml history" # Check if .npmrc or pnpm-workspace.yaml exists echo -e "\n=== pnpm configuration files ===" ls -la .npmrc pnpm-workspace.yaml .pnpmfile.cjs 2>/dev/null || echo "Checking config files..." fd -e "npmrc|pnpmfile|workspace.yaml" .

Repository: ProverCoderAI/effect-template

Length of output: 287

🏁 Script executed:

#!/bin/bash # Check CI workflows for Node.js version echo "=== CI/CD Node.js version requirement ===" find .github -name "*.yml" -o -name "*.yaml" 2>/dev/null | head -5 | xargs grep -l "node-version\|node_version\|setup-node" 2>/dev/null | head -1 | xargs cat 2>/dev/null | grep -A 2 "node-version\|setup-node" || echo "Checking workflows..."

Repository: ProverCoderAI/effect-template

Length of output: 370

Migrate deprecated pnpm configuration to pnpm 11 format.

The pnpm-lock.yaml has been regenerated to v9.0 (pnpm 11 format), but package.json still contains deprecated configuration that is no longer supported in pnpm 11:

ignoredBuiltDependencies and onlyBuiltDependencies must be migrated to the new allowBuilds configuration

Node.js requirement must be explicitly set to 22+ in the engines field (pnpm 11 no longer supports Node.js v18-21)

These deprecated options will cause failures when running pnpm commands. Use the pnpm v10→v11 migration codemod (pnpx codemod run pnpm-v10-to-v11) to complete the migration.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@package.json` at line 6, Update package.json to remove deprecated pnpm v10 fields and adopt pnpm v11 format: replace any ignoredBuiltDependencies and onlyBuiltDependencies entries with the new allowBuilds configuration (mapping allowed package patterns or booleans accordingly) and set the engines.node field to ">=22" (or "22.x" per project policy) so Node.js requirement is explicit for pnpm 11; also keep packageManager set to "pnpm@11.1.2" and run the pnpm v10→v11 codemod (pnpx codemod run pnpm-v10-to-v11) to ensure any other migration changes are applied.

coderabbitai · 2026-05-14T13:55:11Z

+    "@typescript-eslint/parser": "^8.59.3",
+    "typescript-eslint": "^8.59.3",
+    "@vitest/coverage-v8": "^4.1.6",
+    "eslint": "^10.3.0",


⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

🧩 Analysis chain

🌐 Web query:

ESLint 10.0 release notes breaking changes migration guide

💡 Result:

ESLint 10.0 release notes / breaking changes and the official migration guide are here: 1) Official migration guide (v9.x → v10.x) https://eslint.org/docs/latest/use/migrate-to-10.0.0 [1] 2) Official release notes for v10.0.0 https://eslint.org/blog/2026/02/eslint-v10.0.0-released/ [2] Key breaking changes called out in the migration guide (high-signal items) A) Node.js version support dropped ESLint v10.0.0 no longer supports Node.js versions < v20.19.0 (and also drops v21.x and v23.x); the migration guide says to upgrade to Node.js v20.19.0 or later [1][3]. B) “Old config format” no longer supported; flat config required The v10 migration guide states the legacy config system is removed (i.e., old eslintrc format is no longer supported) and points you to use flat config (eslint.config.) [1]. The migration guide summary also calls out removing the eslintrc format [1][3]. C) New configuration file lookup algorithm In ESLint v9 there was an alternate behavior guarded by a feature flag; in v10.0.0, the behavior is the default. The migration guide describes that config lookup now starts from the directory of each linted file and searches upward to the filesystem root (instead of starting from the current working directory) and that the v10_config_lookup_from_file flag was removed [1]. D) Removed feature for eslintrc config lookup behavior flag Attempting to use v10_config_lookup_from_file now results in an error (because the flag was removed) [1]. E) Rule/behavior & API breaking changes (examples listed in the migration guide) The migration guide lists multiple other breaking/API changes, including (among others) removal of the nodeType property in LintMessage objects [1], JSX references now being tracked [1], and changes around fixer APIs requiring string text arguments [1]. How to migrate (practical steps to follow) - Upgrade Node.js to a supported version (>= v20.19.0) before running ESLint 10 [1]. - Ensure you are using flat config (eslint.config.) and remove any legacy eslintrc configuration usage [1]. - If you previously relied on the v9 config lookup behavior / feature flag, update to the new lookup algorithm (start from each linted file’s directory) [1]. - Then run the official migration guide’s checklist/sections to address any remaining listed breaking changes in your specific setup [1].

Citations:

1: https://eslint.org/docs/latest/use/migrate-to-10.0.0

2: https://eslint.org/blog/2026/02/eslint-v10.0.0-released/

3: https://mintlify.com/eslint/eslint/guides/migrate-to-10

🏁 Script executed:

#!/bin/bash # Check ESLint configuration files for compatibility fd eslint.config -e js -e mjs -e cjs --exec cat {}

Repository: ProverCoderAI/effect-template

Length of output: 55

🏁 Script executed:

#!/bin/bash # Check for ESLint configuration files echo "=== Searching for ESLint config files ===" fd -e json -e js -e cjs -e mjs '(eslintrc|eslint\.config)' --base-directory . # Check package.json for Node.js version and ESLint config location echo -e "\n=== Checking packages/app/package.json ===" head -80 packages/app/package.json | tail -20 # Check root package.json for Node.js engines echo -e "\n=== Checking root package.json for engines ===" rg '"engines"' -A 5 package.json

Repository: ProverCoderAI/effect-template

Length of output: 1013

🏁 Script executed:

#!/bin/bash # More comprehensive search for all ESLint-related configs echo "=== Searching for all ESLint configs ===" find . -type f $ -name ".eslintrc*" -o -name "eslint.config.*" $ 2>/dev/null # Check for ESLint in workspace packages echo -e "\n=== Checking eslint references in all package.json files ===" find . -name "package.json" -type f -exec grep -l "eslint" {} \; 2>/dev/null

Repository: ProverCoderAI/effect-template

Length of output: 252

🏁 Script executed:

#!/bin/bash # Check the ESLint flat config file echo "=== Content of eslint.config.mts ===" cat packages/app/eslint.config.mts # Search for Node.js version constraints echo -e "\n=== Searching for Node.js version constraints ===" find . -type f $ -name ".nvmrc" -o -name ".tool-versions" -o -name "nvmrc" $ 2>/dev/null | head -10 # Check GitHub workflows for Node.js version echo -e "\n=== Checking for Node.js version in CI/workflows ===" fd "\.ya?ml$" .github/workflows 2>/dev/null | xargs grep -h "node-version" 2>/dev/null | head -10

Repository: ProverCoderAI/effect-template

Length of output: 10380

🏁 Script executed:

#!/bin/bash # Check if engines field exists in root and app package.json echo "=== Checking engines field in package.json files ===" rg '"engines"' -B 1 -A 3 . --type json # Check for `@eslint/compat` usage in eslint.config.mts echo -e "\n=== Checking `@eslint/compat` usage ===" grep -n "@eslint/compat\|compat" packages/app/eslint.config.mts || echo "No `@eslint/compat` found in config"

Repository: ProverCoderAI/effect-template

Length of output: 219

Add engines field to enforce Node.js >= v20.19.0 for ESLint 10.3.0 compatibility.

The repository has already properly migrated to ESLint's flat config format (eslint.config.mts) and uses @eslint/compat correctly for plugin compatibility. However, ESLint 10.3.0 requires Node.js >= v20.19.0, and this constraint should be explicitly documented in package.json via an engines field. Without it, developers using older Node.js versions may encounter runtime errors. Add to packages/app/package.json:

"engines": { "node": ">=20.19.0" }

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@packages/app/package.json` at line 71, Add an "engines" entry to packages/app/package.json to require Node.js >=20.19.0 so ESLint 10.3.0 runs correctly; locate the existing "eslint": "^10.3.0" dependency in package.json and add an "engines" object with "node": ">=20.19.0" to enforce the minimum Node version for contributors and CI.

renovate Bot assigned skulidropek Feb 19, 2026

renovate Bot requested a review from skulidropek February 19, 2026 08:15

renovate Bot force-pushed the renovate/all branch 12 times, most recently from 6cba843 to 0f055c2 Compare February 26, 2026 20:40

renovate Bot force-pushed the renovate/all branch 9 times, most recently from 92bada8 to 71cb2e1 Compare March 7, 2026 01:14

renovate Bot force-pushed the renovate/all branch 7 times, most recently from 54d829d to 590142f Compare March 13, 2026 18:50

renovate Bot force-pushed the renovate/all branch 7 times, most recently from 5daa077 to 79555ae Compare March 31, 2026 20:40

renovate Bot force-pushed the renovate/all branch 14 times, most recently from 055e1ef to d1673ca Compare April 10, 2026 12:43

renovate Bot force-pushed the renovate/all branch 6 times, most recently from c20c888 to c23139a Compare April 16, 2026 12:07

coderabbitai Bot requested changes May 14, 2026

View reviewed changes

fix(deps): update all dependencies

246bce4

Navigation Menu

Repository navigation

fix(deps): update all dependencies - #31

fix(deps): update all dependencies#31
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all

renovate Bot commented Feb 19, 2026 •

edited

Loading

Uh oh!

coderabbitai Bot commented May 14, 2026 •

edited

Loading

Review skipped

Reviews paused

Changes

Estimated code review effort

Possibly related issues

Uh oh!

coderabbitai Bot left a comment

Uh oh!

Uh oh!

coderabbitai Bot May 14, 2026

Uh oh!

coderabbitai Bot May 14, 2026

Uh oh!

coderabbitai Bot May 14, 2026

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

renovate Bot commented Feb 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

v2.6.6

Patch Changes

v2.6.5

Patch Changes

Configuration

Uh oh!

coderabbitai Bot commented May 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review skipped

Reviews paused

Changes

Estimated code review effort

Possibly related issues

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

coderabbitai Bot May 14, 2026

Choose a reason for hiding this comment

Uh oh!

coderabbitai Bot May 14, 2026

Choose a reason for hiding this comment

Uh oh!

coderabbitai Bot May 14, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

renovate Bot commented Feb 19, 2026 •

edited

Loading

`v2.6.6`

`v2.6.5`

coderabbitai Bot commented May 14, 2026 •

edited

Loading