Repository navigation
fix(deps): update all dependencies - #20
renovate[bot] wants to merge 1 commit into
Conversation
61f06bc to
4c58bf8
Compare
52aba09 to
16d549f
Compare
f240877 to
3c2e51f
Compare
9456c54 to
0ff8d9f
Compare
6ff8486 to
4c77644
Compare
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
| Layer / File(s) | Summary |
|---|---|
GitHub Actions versions .github/actions/setup/action.yml, .github/workflows/checking-dependencies.yml, .github/workflows/snapshot.yml |
pnpm action bumped to @v6 in composite and workflow; actions/setup-node Node input updated to 24.15.0; artifact upload action bumped to actions/upload-artifact@v7. |
pnpm version pins package.json, packages/app/package.json |
Workspace and app packageManager updated from pnpm@10.30.1 to pnpm@11.1.2. |
Dependency and toolchain upgrades package.json, packages/app/package.json |
Root Changesets packages (@changesets/changelog-github, @changesets/cli) bumped; app package dependencies and devDependencies refreshed (Effect packages, ts-morph, Biome/ESLint, TypeScript tooling, Vitest/Vite, etc.). |
Estimated code review effort
🎯 3 (Moderate) | ⏱️ ~20 minutes
Possibly related issues
- Dependency Dashboard effect-template#10: Overlaps pnpm/action-setup, pnpm pinning, and tooling/version updates.
- Dependency Dashboard eslint-plugin-suggest-members#2: Matches workflow and pnpm/tooling bumps in CI and manifests.
- Dependency Dashboard #1: Mirrors the same workflow and package.json version updates.
- Dependency Dashboard dist-deps-prune#2: Contains similar dependency/version bump changes (pnpm, actions, packages).
- Dependency Dashboard context-doc#5: Renovate-style workflow and package pin bumps align with that issue.
- Dependency Dashboard effect-eslint-template#6: Shares pnpm and ESLint/Biome/tooling dependency updates.
🚥 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. Description check ✅ Passed The description clearly documents the Renovate dependency, package manager, and GitHub Actions updates in the changeset. Title check ✅ Passed The title accurately identifies the pull request as a broad dependency update, including packages, tooling, and GitHub Actions.
-
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.
🐇 I nudged a YAML line, made pnpm climb to eleven,
Actions hum a newer tune, workflows light as heaven.
Packages refreshed, linters wake and play,
Tests tiptoe cleaner paths, building through the day.
✨
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 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 workflow currently uses a mutable tag "pnpm/action-setup@v6";
replace that with an immutable full commit SHA (40-hex) for pnpm/action-setup to
pin the action (e.g., "pnpm/action-setup@<full-commit-sha>"). Locate the "uses:
pnpm/action-setup@v6" entry in the action.yml and update it to the exact commit
SHA from the pnpm/action-setup repository, verify the SHA is full-length (40
characters) and that the workflow still runs correctly after the change.
In @.github/workflows/checking-dependencies.yml:
- Line 15: Replace the mutable tag reference "uses: pnpm/action-setup@v6" with
an immutable pin to the full commit SHA for the pnpm/action-setup action (e.g.,
"uses: pnpm/action-setup@<full-commit-sha>"); locate the occurrences of
"pnpm/action-setup@v6" in the workflow and update them to the corresponding
release commit SHA from the action's repository, then verify the workflow runs
successfully.
🪄 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: 4cd2e52a-a23f-4849-8bc7-20b25e799703
⛔ 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: | ||
| - name: Install pnpm | ||
| uses: pnpm/action-setup@v3 | ||
| uses: pnpm/action-setup@v6 |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify mutable action refs under .github (tag-based refs like `@v1/`@v6).
# Expected: no matches after SHA pinning.
rg -n --iglob '*.yml' --iglob '*.yaml' 'uses:\s*[^@[:space:]]+@v[0-9]+(\.[0-9]+){0,2}\b' .githubRepository: ProverCoderAI/openapi-effect
Length of output: 1009
Pin pnpm/action-setup to an immutable commit SHA.
Line 13 uses a mutable tag (@v6). Please pin to a full-length commit SHA to reduce supply-chain risk and avoid policy breaks in hardened org settings.
🔒 Suggested change
- uses: pnpm/action-setup@v6
+ uses: pnpm/action-setup@<full-length-commit-sha> # v6.xReference: https://docs.github.com/actions/security-guides/security-hardening-for-github-actions
🤖 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/actions/setup/action.yml at line 13, The workflow currently uses a
mutable tag "pnpm/action-setup@v6"; replace that with an immutable full commit
SHA (40-hex) for pnpm/action-setup to pin the action (e.g.,
"pnpm/action-setup@<full-commit-sha>"). Locate the "uses: pnpm/action-setup@v6"
entry in the action.yml and update it to the exact commit SHA from the
pnpm/action-setup repository, verify the SHA is full-length (40 characters) and
that the workflow still runs correctly after the change.
| steps: | ||
| - uses: actions/checkout@v6 | ||
| - uses: pnpm/action-setup@v4 | ||
| - uses: pnpm/action-setup@v6 |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify mutable action refs under .github (tag-based refs like `@v1/`@v6).
# Expected: no matches after SHA pinning.
rg -n --iglob '*.yml' --iglob '*.yaml' 'uses:\s*[^@[:space:]]+@v[0-9]+(\.[0-9]+){0,2}\b' .githubRepository: ProverCoderAI/openapi-effect
Length of output: 1009
Pin pnpm/action-setup to a commit SHA instead of a mutable tag.
Line 15 uses @v6, which is a mutable tag reference. Per GitHub's security hardening guidelines, action references should be pinned to full commit SHAs to ensure immutability and prevent unintended updates from tag rewrites.
🤖 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, Replace the mutable
tag reference "uses: pnpm/action-setup@v6" with an immutable pin to the full
commit SHA for the pnpm/action-setup action (e.g., "uses:
pnpm/action-setup@<full-commit-sha>"); locate the occurrences of
"pnpm/action-setup@v6" in the workflow and update them to the corresponding
release commit SHA from the action's repository, then verify the workflow runs
successfully.
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 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 `@package.json`:
- Line 6: The package.json currently sets "packageManager": "pnpm@11.1.2" but
pnpm v11 requires config and environment changes; run the recommended codemod
(pnpx codemod run pnpm-v10-to-v11) and then: move any settings under the
package.json "pnpm" field into pnpm-workspace.yaml, strip .npmrc to only
auth/registry entries, update .nvmrc and CI to Node.js 22+ to match pnpm v11,
rename any environment variables from npm_config_* to pnpm_config_ and manually
review remaining envs, and rename or invoke scripts named
clean/setup/deploy/rebuild using pnpm pm to avoid shadowing built-ins.
🪄 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: 78ded05a-1811-4eac-8349-84f29cb8618e
⛔ 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
🚧 Files skipped from review as they are similar to previous changes (4)
- .github/actions/setup/action.yml
- .github/workflows/checking-dependencies.yml
- .github/workflows/snapshot.yml
- packages/app/package.json
| "private": true, | ||
| "description": "Monorepo workspace for effect-template", | ||
| "packageManager": "pnpm@10.30.1", | ||
| "packageManager": "pnpm@11.1.2", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
pnpm 11 breaking changes and migration guide
💡 Result:
pnpm 11 is a major release that introduces significant breaking changes, security-first defaults, and architectural improvements [1]. The official migration guide is available at https://pnpm.io/11.x/migration [2]. Key Breaking Changes and Migration Steps Configuration Changes pnpm 11 significantly changes how configuration is handled [3][1]: - Configuration is no longer read from the pnpm field in package.json; move these settings to pnpm-workspace.yaml [3][2]. -.npmrc files are now restricted to auth and registry settings only [3][1]. All other settings (e.g., hoist-pattern, node-linker) must be moved to pnpm-workspace.yaml using camelCase keys [3][2]. - npm_config_* environment variables are no longer supported; rename them to pnpm_config_* [3][1]. - pnpm no longer reads npm's global config at $PREFIX/etc/npmrc [1]. Dependency and Script Management - Build-dependency settings (onlyBuiltDependencies, neverBuiltDependencies, etc.) are consolidated into a single allowBuilds map in pnpm-workspace.yaml [3][1]. - Package manager strictness settings are collapsed into a single pmOnFail setting [3][2]. - Script names now shadow built-in commands [3]. If you have scripts named clean, setup, deploy, or rebuild, pnpm will execute your script instead of the built-in command; use pnpm pm to access the built-in version [3]. - pnpm install -g (with no arguments) is no longer supported; use pnpm add -g instead [3][1]. Environment and Infrastructure - Node.js 18, 19, 20, and 21 are no longer supported; Node.js 22+ is required [1]. - pnpm is now distributed as pure ESM [1]. - Global installs are now isolated using a global-virtual-store, preventing interference between global packages [1]. Security and New Features - Minimum Release Age: By default, pnpm 11 blocks the installation of package versions published within the last 24 hours to mitigate supply chain attacks [4][5][6]. - Exotic Subdependencies: pnpm 11 blocks dependencies resolved from non-standard sources (e.g., Git repositories or direct tarball URLs) by default [4][6]. - Native Publish: The npm CLI fallback for publishing has been removed in favor of a native implementation [1]. - Store Index: The store index has been migrated from a JSON-per-package format to a single SQLite database for improved performance [1][5]. Migration Tooling The pnpm team provides a codemod to automate many of these changes [2]. You can run it in your project directory: pnpx codemod run pnpm-v10-to-v11 [2] For changes that cannot be automated, such as environment variable updates, manual review is required [3][2].
Citations:
- 1: https://pnpm.io/blog/releases/11.0
- 2: https://pnpm.io/11.x/migration
- 3: https://pnpm.io/migration
- 4: https://gbhackers.com/pnpm-11-enables-default-release-age-guard/
- 5: https://cyberpress.org/pnpm-blocks-supply-attacks/
- 6: https://undercodenews.com/pnpm-11-reinvents-javascript-security-a-new-era-for-dependency-protection/
🌐 Web query:
pnpm 11.1.2 release notes and security advisories
💡 Result:
As of May 17, 2026, pnpm version 11.1.2 is the latest release [1]. Release Notes for pnpm 11.1.2 Specific release notes for version 11.1.2 were not explicitly detailed in the provided search results, as it is a very recent patch release [1]. However, it follows the major 11.1.0 and 11.1.1 releases, which introduced several significant features and fixes [2][3][4]: - New Commands: Added pnpm audit signatures (to verify ECDSA registry signatures), pnpm bugs (to open package bug trackers), and pnpm owner (to manage package owners) [3][4]. - Named Registries: Added support for installing packages from arbitrary named registries, including a built-in gh: prefix for the GitHub Packages npm registry [3][4]. - CI Improvements: Introduced the --no-runtime flag (config: runtime=false) to skip installing runtime entries (e.g., Node.js) in CI environments [3][4]. - Fixes: Version 11.1.1 included fixes for installability validation in workspace projects, resolved issues with pnpm add for named registries, and updated @zkochan/cmd-shim to improve compatibility with Git Bash on Windows [2]. Security Advisories There are no specific security advisories listed for version 11.1.2. Users should monitor the official pnpm GitHub Security Advisories page for any future disclosures [5]. Recent security-related updates in the pnpm 11 series include: - Minimum Release Age: pnpm 11 introduced a default Minimum Release Age of 24 hours (1440 minutes), which prevents the installation of newly published package versions to mitigate supply chain attacks [6][7][8]. - Enhanced Auditing: pnpm audit now queries the registry's bulk security advisories endpoint and filters by GitHub Advisory ID (GHSA) rather than CVE identifiers [9]. - Security Hardening: pnpm 11 requires Node.js 22+ and is distributed as pure ESM [10][11]. It also includes improved control over lifecycle scripts via the allowBuilds model [7][8]. For the most up-to-date information, always check the official pnpm releases page on GitHub and the security advisories section [12][5].
Citations:
- 1: https://www.npmjs.com/package/pnpm?activeTab=versions
- 2: https://github.com/pnpm/pnpm/releases/tag/v11.1.1
- 3: https://pnpm.io/blog/releases/11.1
- 4: https://newreleases.io/project/npm/pnpm/release/11.1.0
- 5: https://github.com/pnpm/pnpm/security/advisories
- 6: https://gbhackers.com/pnpm-11-enables-default-release-age-guard/
- 7: https://undercodenews.com/pnpm-11-reinvents-javascript-security-a-new-era-for-dependency-protection/
- 8: https://pnpm.io/supply-chain-security
- 9: https://pnpm.io/cli/audit
- 10: https://github.com/pnpm/pnpm/releases/tag/v11.0.0
- 11: https://pnpm.io/blog/releases/11.0
- 12: https://github.com/pnpm/pnpm/releases
Review pnpm 11 migration requirements before merging.
This major version upgrade introduces breaking changes that require configuration updates and environment adjustments:
- Configuration files: Settings in
package.json'spnpmfield must move topnpm-workspace.yaml. Update.npmrcto contain only auth and registry settings. - Node.js requirement: pnpm 11 requires Node.js 22+. Verify your project's
.nvmrcand CI configuration specify a compatible version. - Environment variables: Any
npm_config_*variables must be renamed topnpm_config_*. - Script behavior: Scripts named
clean,setup,deploy, orrebuildnow shadow built-in commands; usepnpm pmto access built-in versions.
Run the migration codemod to automate configuration changes:
pnpx codemod run pnpm-v10-to-v11
Refer to https://pnpm.io/11.x/migration for the complete migration guide. Manual review is needed for environment variable updates that the codemod cannot automate.
🤖 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, The package.json currently sets "packageManager":
"pnpm@11.1.2" but pnpm v11 requires config and environment changes; run the
recommended codemod (pnpx codemod run pnpm-v10-to-v11) and then: move any
settings under the package.json "pnpm" field into pnpm-workspace.yaml, strip
.npmrc to only auth/registry entries, update .nvmrc and CI to Node.js 22+ to
match pnpm v11, rename any environment variables from npm_config_* to
pnpm_config_ and manually review remaining envs, and rename or invoke scripts
named clean/setup/deploy/rebuild using pnpm pm to avoid shadowing built-ins.
|
Надо смержить сюда main ветку и исправить все ошибки в CI/CD что бы код был с актуальными библиотеками |
|
🤖 AI Work Session Started Starting automated work session at 2026-06-19T19:17:51.406Z The PR has been converted to draft mode while work is in progress. This comment marks the beginning of an AI work session. Please wait for the session to finish, and provide your feedback. |
|
Update: the CI/CD fix is implemented and verified, but I cannot push it directly to this PR head branch. Blocker:
Prepared fix:
What the fix covers:
Verification:
Needed human action: either grant/push access to |
🤖 Solution Draft LogThis log file contains the complete execution trace of the AI solution draft process. 💰 Cost estimation:
📊 Context and tokens usage:
Total: (508.9K + 13.1M cached) input tokens, 68.4K output tokens, $21.304392 cost 🤖 Models used:
📎 Log file uploaded as Repository (75696KB)Now working session is ended, feel free to review and add any feedback on the solution draft. |
🔄 Auto-restart triggered (iteration 1)Reason: CI failures detected Starting new session to address the issues. Auto-restart-until-mergeable mode is active. This run will stop after 5 restart iterations. |
|
Rechecked the failing CI/CD status in this restart session. Findings:
Verification repeated locally with Node
Fork CI also has successful runs for Remaining blocker is repository permissions, not code: |
🔄 Auto-restart-until-mergeable Log (iteration 1)This log file contains the complete execution trace of the AI solution draft process. 💰 Cost estimation:
🤖 Models used:
📎 Log file uploaded as Repository (96784KB)Now working session is ended, feel free to review and add any feedback on the solution draft. |
🔄 Auto-restart triggered (iteration 2)Reason: CI failures detected Starting new session to address the issues. Auto-restart-until-mergeable mode is active. This run will stop after 5 restart iterations. |
|
Rechecked and updated the prepared fix in this restart session. Current prepared commit:
Root causes confirmed from upstream CI logs for old SHA
Verification on current SHA
Remaining blocker is repository permission, not code. Needed maintainer action: push/cherry-pick |
🔄 Auto-restart-until-mergeable Log (iteration 2)This log file contains the complete execution trace of the AI solution draft process. 💰 Cost estimation:
🤖 Models used:
📎 Log file uploaded as Repository (2 chunks) (116514KB)Now working session is ended, feel free to review and add any feedback on the solution draft. |
🔄 Auto-restart triggered (iteration 3)Reason: CI failures detected Starting new session to address the issues. Auto-restart-until-mergeable mode is active. This run will stop after 5 restart iterations. |
|
Restart iteration 3 rechecked the prepared CI fix. Current verified head:
Fresh upstream CI logs downloaded in this session confirm old-head root causes:
Verification repeated on
Push blocker remains external: Needed maintainer action: push or cherry-pick |
🔄 Auto-restart-until-mergeable Log (iteration 3)This log file contains the complete execution trace of the AI solution draft process. 💰 Cost estimation:
🤖 Models used:
📎 Log file uploaded as Repository (2 chunks) (139990KB)Now working session is ended, feel free to review and add any feedback on the solution draft. |
🔄 Auto-restart triggered (iteration 4)Reason: CI failures detected Starting new session to address the issues. Auto-restart-until-mergeable mode is active. This run will stop after 5 restart iterations. |
|
Restart iteration 4 rechecked the CI/CD fix. Current verified head:
Fresh upstream logs downloaded in this session confirm the old-head failures:
Verification repeated locally on
Push status:
Needed maintainer action: push or cherry-pick |
🔄 Auto-restart-until-mergeable Log (iteration 4)This log file contains the complete execution trace of the AI solution draft process. 💰 Cost estimation:
🤖 Models used:
📎 Log file uploaded as Repository (2 chunks) (154923KB)Now working session is ended, feel free to review and add any feedback on the solution draft. |
🔄 Auto-restart triggered (iteration 5)Reason: CI failures detected Starting new session to address the issues. Auto-restart-until-mergeable mode is active. This run will stop after 5 restart iterations. |
|
Restart iteration 5 rechecked the CI/CD failures and the prepared fix. Current verified fix:
Fresh upstream CI status:
Root causes confirmed from downloaded upstream logs:
Verification repeated locally on
Fork CI on
Push status:
Needed maintainer action: push or cherry-pick |
🔄 Auto-restart-until-mergeable Log (iteration 5)This log file contains the complete execution trace of the AI solution draft process. 💰 Cost estimation:
🤖 Models used:
📎 Log file uploaded as Repository (2 chunks) (177139KB)Now working session is ended, feel free to review and add any feedback on the solution draft. |
|
|
🤖 AI Work Session Completed Work session ended at 2026-06-19T20:58:19.771Z The PR will be converted back to ready for review. This comment marks the end of an AI work session. New comments after this time will be considered as feedback. |
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
^2.4.4→^2.6.8^0.5.2→^1.0.1^2.29.8→^3.0.3^4.6.0→^4.8.12.0.2→2.1.13.3.3→3.3.7^24.10.13→^26.6.6^8.56.0→^8.73.0^8.56.0→^8.73.0^4.0.18→^5.1.1^1.6.9→^1.6.28v6→v7v6→v7v6→v7^3.19.18→^4.1.4^10.0.1→^10.15.0^4.4.4→^4.4.5^12.1.1→^14.0.0^4.0.0→^4.2.2^63.0.0→^80.0.0^17.3.0→^17.14.0^4.0.8→^5.4.324.13.1→26.13.110.30.1→12.21.0v4→v6v3→v6^5.9.3→^7.0.2^8.56.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
dcb1eabThanks @dyc3! - Improved the performance of linting JavaScript and HTML files when Tailwind rules are enabled.#13094
ae66383Thanks @dyc3! - Fixed #12994: the HTML formatter no longer moves a word onto its own line when it follows an inline element or{expression}that starts a line. Formatting such text is now stable after one pass.<span> Showing the first {shown} of - {total} - references + {total} references </span>#13162
854ff15Thanks @Punisheroot! - Fixed #13125:noUselessThisAliasno longer reports aliases used in instance and static class field initializers, where replacing the alias withthischanges which object is accessed.#12059
87784c7Thanks @dyc3! - Fixed type inference for the intersection of a primitive type and one of its literal types, such asstring & "a", which Biome inferred asneverinstead of"a". Type-aware rules such asuseExhaustiveSwitchCasesandnoFloatingPromisesnow see the literal, so the following switch is reported for missing the"a"case.#12551
ca039a1Thanks @pkallos! - Fixed #9842:useNullishCoalescingno longer skips||and||=inside a call to a locally declaredBooleanwhenignoreBooleanCoercionis enabled.v2.6.7Compare Source
Patch Changes
#12906
b3375d2Thanks @dyc3! - Added the nursery rulenoAsyncPromiseFinally, which reports async functions passed to a promise's.finally()method. If such a function fails, its error replaces the original result or error of the promise.#12894
e24da6fThanks @dyc3! - Added the nursery rulenoDuplicateTypeConstituents, which reports types listed more than once in a union or intersection type, andundefinedin the type of an optional parameter.#12899
6c15027Thanks @dyc3! - Added the nursery rulenoExcessiveSelectorComplexity, which limits how many IDs, type selectors, attribute selectors, pseudo-classes, universal selectors, compound selectors, and combinators a CSS selector can contain. It can also disallow chosen combinators, pseudo-classes, pseudo-elements, attributes, and attribute operators. The rule does nothing until an option is set.For example, with
"maxIds": 1, the following selector is reported:#12897
0b8f429Thanks @dyc3! - Added the new nursery rulenoInvalidFetchOptions, which reports abodyin the options offetch()andnew Request()when the method isGETorHEAD. These calls throw aTypeErrorat runtime. When nomethodis given, the request usesGET.#12926
9b6b9f4Thanks @dyc3! - Added the nursery rulenoNewArray, which reportsnew Array()calls with a single argument. Such a call creates an empty array of the given length when the argument is a number, and an array that holds the argument otherwise.#12895
739440fThanks @dyc3! - Added the new nursery rulenoRedundantTypeConstituents, which reports members of union and intersection types that have no effect, such as a literal type next to its primitive type, orneverin a union.#12810 [
71ab61b](https://redirect.github.cConfiguration
📅 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.