Repository navigation
fix(deps): update all dependencies - #31
renovate[bot] wants to merge 1 commit into
Conversation
6cba843 to
0f055c2
Compare
92bada8 to
71cb2e1
Compare
54d829d to
590142f
Compare
5daa077 to
79555ae
Compare
055e1ef to
d1673ca
Compare
c20c888 to
c23139a
Compare
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
| 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 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.
🐰 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 🥕
There was a problem hiding this comment.
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
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (5)
.github/actions/setup/action.yml.github/workflows/checking-dependencies.yml.github/workflows/snapshot.ymlpackage.jsonpackages/app/package.json
| steps: | ||
| - uses: actions/checkout@v6 | ||
| - uses: pnpm/action-setup@v4 | ||
| - uses: pnpm/action-setup@v6 |
There was a problem hiding this comment.
🧩 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 yamlRepository: 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 yamlRepository: 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
fiRepository: 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:
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.
| "private": true, | ||
| "description": "Monorepo workspace for effect-template", | ||
| "packageManager": "pnpm@10.29.3", | ||
| "packageManager": "pnpm@11.1.2", |
There was a problem hiding this comment.
🧩 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 -50Repository: 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:
ignoredBuiltDependenciesandonlyBuiltDependenciesmust be migrated to the newallowBuildsconfiguration- Node.js requirement must be explicitly set to 22+ in the
enginesfield (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.
| "@typescript-eslint/parser": "^8.59.3", | ||
| "typescript-eslint": "^8.59.3", | ||
| "@vitest/coverage-v8": "^4.1.6", | ||
| "eslint": "^10.3.0", |
There was a problem hiding this comment.
🧩 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.jsonRepository: 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/nullRepository: 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 -10Repository: 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.
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
^2.4.0→^2.6.8^0.5.2→^1.0.1^2.29.8→^3.0.3^0.73.2→^0.77.2^0.56.4→^0.60.2^0.58.0→^0.61.1^0.94.5→^0.97.2^0.104.1→^4.1.4^0.47.0→^0.51.0^0.47.0→^0.51.0^0.73.1→^0.76.2^0.49.0→^0.52.1^0.38.0→^0.41.0^0.27.0→^4.1.4^0.16.0→^0.19.1^4.6.0→^4.8.12.0.2→2.1.13.3.3→3.3.7^0.0.25→^0.0.26^24.10.13→^26.6.6^8.55.0→^8.73.0^8.55.0→^8.73.0^4.0.18→^5.1.1^1.6.9→^1.6.28v6→v7v6→v7v6→v7^3.19.17→^4.1.4^10.0.0→^10.15.0^4.4.4→^4.4.5^12.1.1→^14.0.0^3.0.7→^4.2.2^2.0.0→^3.0.0^63.0.0→^80.0.0^17.3.0→^17.14.0^4.0.8→^5.4.324.13.1→26.13.110.29.3→12.21.0v4→v6v3→v6^27.0.2→^28.0.0^5.9.3→^7.0.2^8.55.0→^8.73.0^7.3.1→^8.3.8^4.0.18→^5.1.1cc @skulidropek
Release Notes
biomejs/biome (@biomejs/biome)
v2.6.8Compare Source
Patch Changes
#13080
a68137dThanks @dyc3! - Added the nursery rulenoBufferConstructor, which disallows the deprecated Node.jsBuffer()andnew Buffer()constructors. UseBuffer.from(),Buffer.alloc(), orBuffer.allocUnsafe()instead.#12966
82651f5Thanks @dyc3! - Added the nursery rulenoConfusingArraySplice, which reportssplice()andtoSpliced()calls that replace a single element or insert at index-1.#12924
0a9d204Thanks @dyc3! - Added the nursery rulenoDynamicRequire, which disallowsrequire()calls whose module name is built at runtime. When thecheckDynamicImportsoption is enabled, the rule also checksimport()calls.#12907
6f2635aThanks @dyc3! - Added the nursery rulenoLateCurrentTargetAccess, which reports reads ofevent.currentTargetthat run after the browser has finished handling the event, whencurrentTargetisnull.#12904
04f30c4Thanks @dyc3! - Added the nursery rulenoMisusedSpread, which uses type information to report spreads that produce unexpected results: strings spread into arrays or arguments, and promises, functions, maps, arrays, iterables, class instances, and classes spread into objects or JSX attributes.#12893
5d7ca32Thanks @dyc3! - Added the nursery rulenoTripleSlashReference, which reports/// <reference path="..." />comments and/// <reference types="..." />comments for packages that the file also imports. Thelib,path, andtypesoptions control which kinds of references are allowed./// <reference path="./globals.d.ts" />#12561
746c421Thanks @dyc3! - Added the nursery rulenoVueAsyncComputed, which reports asynchronous code in Vue computed properties, such asasyncfunctions,await, promises,setTimeout(), andnextTick().#12964
149d729Thanks @dyc3! - Added the nursery rulenoVueDefineModelDefault, which disallows thedefaultoption in Vue'sdefineModel(). When a parent component passesundefinedwithv-model, the child component uses the default value while the parent keepsundefined, so the two components show different values.#13060
67bc9d5Thanks @dyc3! - Added the nursery rulenoVueDeprecatedFilter, which reports the filter syntax that Vue 3 removed.For example, the following template uses the
currencyfilter:#12545
0bbe4f1Thanks @dyc3! - Added the new nursery rulenoVueDeprecatedVIs, which reports the deprecated Vuev-isdirective. Use theisattribute with avue:prefix instead.#12580
3fdc987Thanks @dyc3! - Added the nursery rulenoVueExportInScriptSetup, which disallowsexportin Vue<script setup>blocks. Vue fails to compile a component when its<script setup>block exports a value. TypeScript type exports are allowed.#13063
d4e90c8Thanks @dyc3! - Added the nursery rulenoYamlEmptyMapKeys, which reports YAML map entries whose key is missing, or has only a tag or an anchor. The rule is recommended.: value#13061
97aa183Thanks @dyc3! - Added the nursery rulenoYamlEmptyMapValues, which reports keys in YAML maps that have no value.name:#13062
6aad75fThanks @dyc3! - Added the new nursery rulenoYamlEmptySequenceEntries, which reports empty items in YAML lists.#13082
c1c8c85Thanks @dyc3! - Added the nursery ruleuseCalledWith, which reportstoHaveBeenCalled(),toBeCalled(), andtoHaveBeenCalledOnce()assertions, because they don't check the arguments that the function was called with. The rule belongs to thetestdomain.#13075
acfeaf9Thanks @dyc3! - Added the nursery ruleuseExpectToHaveBeenCalled, which reports tests that compare the number of calls of a mock function to zero, and suggests usingtoHaveBeenCalled()instead.#13076
cf5b1a6Thanks @dyc3! - Added the nursery ruleuseExpectToHaveBeenCalledTimes, which reports tests that check the length ofmock.callswithtoHaveLength(), and suggests usingtoHaveBeenCalledTimes()instead.#13020
5d28641Thanks @dyc3! - Added the new nursery ruleusePackageJsonValidLicense, which reports alicensefield inpackage.jsonthat isn't a valid license. The rule accepts SPDX license identifiers and expressions,UNLICENSED, and references to a license file such asSEE LICENSE IN LICENSE.md.For example, the rule reports the following
package.jsonfile becauseGPL3isn't an SPDX license identifier:{ "name": "my-package", "license": "GPL3" }#13079
058d7a1Thanks @dyc3! - Added the nursery ruleuseSpyOn, which reports properties that are overwritten withjest.fn()orvi.fn(). Overwriting a property loses its original value, whilejest.spyOn()andvi.spyOn()keep it so it can be restored after the test.#13081
be58f67Thanks @dyc3! - Added the nursery ruleuseTopLevelRequire, which reportsrequire()calls that aren't at the top level of the module, such as calls inside functions, blocks, ortrystatements.#13054
4d81f0dThanks @dyc3! - Added the nursery ruleuseValidNamespaceImports, which reports names read from a namespace import that the imported module doesn't export. It also reports assignments to members of a namespace import, and namespace imports of modules that have no exports.#13058
ae251e4Thanks @dyc3! - Added the new nursery ruleuseVueConsistentVOnHandlerStyle, which enforces one style of event handler in Vuev-ondirectives. By default, it prefers the name of a method, and an inline function where a method name can't be used.#12965
c33c03dThanks @dyc3! - Added the nursery ruleuseVueRegisteredComponentNameCasing, which requires the names of components registered in thecomponentsoption of a Vue component to use one casing style. By default, names must be in PascalCase. Thecasingoption switches the rule to camelCase or kebab-case.#12145
596a2b1Thanks @ematipico! - Added type narrowing for unwritten locallet/constvariables and parameters aftertypeof, equality, nullish, and truthiness checks. Type-aware rules now use these refinements in branches, short-circuit expressions, and after early returns, includingnoUnnecessaryConditionsandnoFloatingPromises. Types such as{}no longer imply that a value is always truthy.#12935
e506ff1Thanks @dyc3! - Improved the performance of the rulesnoRedeclareandnoUnsafeDeclarationMerging.biome lintwith Biome's default rules is now about 3% to 5% faster on large projects, and up to 11% faster on some TypeScript projects.#13181
e1556aeThanks @dyc3! - Fixed the HTML formatter printing a comment twice when it ends the line of an element's opening tag. For example,<div><!-- comment -->followed by<i>x</i></div>on the next line is now formatted as:#13130
1b350edThanks @dyc3! - Fixed #13107: the unsafe fix ofnoDistractingElementsnow removes the whole element, including its closing tag and children, instead of only the opening tag. The fix is no longer offered when removing the element would produce invalid code, such asconst Ticker = () => <marquee>News</marquee>;.#13054
4d81f0dThanks @dyc3! - FixednoUnresolvedImportsreporting names that a module re-exports from a CommonJS module or from a file that isn't JavaScript, such asexport { foo } from "./legacy.cjs". The rule now also reports default imports from a module that only re-exports another module withexport * from, becauseexport * fromdoesn't forward the default export.#12602
d5da394Thanks @dyc3! - Fixed #12600:biome lint --suppressnow adds suppression comments for diagnostics emitted by plugins, such as// biome-ignore lint/plugin/noFoo: ignored using `--suppress`.#13097
3be9e3dThanks @ashokram-si! - Fixed #13064: ThenoUnknownTypeSelectorrule now correctly accepts the valid<selectedcontent>HTML element used in customizable select controls.#13181
e1556aeThanks @dyc3! - Fixed #13167: The HTML formatter no longer deletes comments that follow a Svelte block delimiter on the same line, such as{#if},{:else}, or{#each}. For example,{#if a}<!-- comment --><i>x</i>{/if}is now formatted as:{#if a} - <i>x</i> + <!-- comment --><i>x</i> {/if}#12845
e3ab04dThanks @dyc3! - Fixed the location of Tailwind CSS diagnostics reported on unquoted object keys. Inclsx({ shadow: active }), diagnostics now highlightshadowinstead of starting one character later athadow:.#13098
d3be626Thanks @ashokram-si! - Fixed #13084: TheuseThisInClassMethodsrule now correctly recognizesthiswhen used inside parameter default values for methods, setters, and class fields.#13131
a788cacThanks @dyc3! - Fixed #13129: the fix ofuseArrowFunctionno longer produces invalid code when the function is in the initializer of aforstatement and returns aninexpression. The arrow function body is now wrapped in parentheses.#12840
8908627Thanks @dyc3! - Fixed #12796:useMathMinMaxno longer reports comparisons with abigintwritten as an expression, such as-1nor2n ** 62n - 1n, or with aconstvariable initialized with one. Its unsafe fix turned these comparisons intoMath.min()orMath.max()calls, which throw aTypeErrorwhen given abigint.#13152
61924f6Thanks @dyc3! - FixednoVueWatchAfterAwait,noVueLifecycleAfterAwaitandnoVueRestrictedCallAfterAwait, which now also check thesetup()function passed as the first argument ofdefineComponent(). The following code is now reported:When
defineComponent()receives both a function and an options object, these rules now ignore thesetupoption, because Vue runs the function instead.#13152
61924f6Thanks @dyc3! -noVueDuplicateKeysnow checks the properties returned by asetup()method of an options object, soreturn { foo }conflicts with a prop, data property, method or computed property namedfoo.#13152
61924f6Thanks @dyc3! - The Vue emit rules now read events declared with a function type, as indefineEmits<(e: "change", value: string) => void>(), and event names written as template literals without substitutions, as inemit(`change`).noVueUndeclaredEmits,noVueUnusedEmitDeclarations,useVueSingleEventPayloadanduseVueEmitValidatorpreviously skipped events declared in these forms.noVueShadowNativeEventsnow checksthis.$emit()only wherethisis the component, and no longer reports$emit()called through a variable that holdsthis, as inconst vm = this; vm.$emit("click").#12947
a54965dThanks @machadinhos! - Added the nursery rulenoDrizzleDbObjectInsideTransaction, which reports a Drizzle ORM instance used inside its own transaction callback instead of the transaction object.#13123
e7c8297Thanks @ematipico! - Fixed #12176: type-aware rules now select the matching overload of a method declared several times in an interface or object type. For example,useAwaitThenableno longer reportsawait app.listen({ port: 0 })on a Fastify server, and still reportsawait app.listen({ port: 0 }, callback).#12059
87784c7Thanks @dyc3! - FixednoUnsafePlusOperandstreating the negation of abigintvalue as anumber. Code such as-value + 1n, wherevalueis declared asbigint, is no longer reported for mixingnumberandbigint.#13151
be372b5Thanks @dyc3! - Fixed Vue lint rules such asuseVueVModelanduseVueVOnExacttreating MathML elements like<math>and<mi>as components. Biome now recognizes the MathML Core elements as native elements, and in Vue, Svelte, and Astro files it treats known hyphenated elements such as<annotation-xml>and the SVG<font-face>as native elements instead of components.#12059
87784c7Thanks @dyc3! - Type inference now evaluates conditional types such asT extends U ? X : Y, includinginferand distribution over unions, instead of treating them as a union of both branches. This also applies to built-in types such asExclude,Extract,ReturnType,Parameters, andAwaited, which improves the accuracy of type-aware rules such asnoFloatingPromises.#12602
d5da394Thanks @dyc3! - Biome now reports an error when a GritQL plugin file name contains invalid characters that could conflict with Biome suppressions.#12838
81d8d28Thanks @dyc3! - Added the nursery rulenoTailwindRestrictedClassesfor JavaScript and HTML. It reports the Tailwind CSS classes and variants listed in its options with a custom message, and can replace them with a configured class or variant.{ "linter": { "rules": { "nursery": { "noTailwindRestrictedClasses": { "level": "error", "options": { "classes": { "bg-green-500": { "message": "Use the success color.", "use": "bg-success" }, "float-*": "Use flexbox or grid for layout." } } } } } } }#12932
68e6887Thanks @dyc3! - Improved the performance of linting files that have no suppression comments by up to 61%.#13136 [
dcb1eab](https://redirect.github.com/biomConfiguration
📅 Schedule: (UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.