Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Nov 1, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@azure-tools/typespec-autorest (source) ^0.61.0 -> ^0.62.0 age adoption passing confidence devDependencies minor
@azure-tools/typespec-azure-core (source) ^0.61.0 -> ^0.62.0 age adoption passing confidence devDependencies minor
@azure-tools/typespec-azure-resource-manager (source) ^0.61.0 -> ^0.62.0 age adoption passing confidence devDependencies minor
@azure-tools/typespec-client-generator-core (source) ^0.61.0 -> ^0.62.0 age adoption passing confidence devDependencies minor
@biomejs/biome (source) 2.2.6 -> 2.3.5 age adoption passing confidence dependencies minor
@biomejs/biome (source) 2.2.6 -> 2.3.5 age adoption passing confidence devDependencies minor
@biomejs/js-api (source) 3.0.0 -> 4.0.0 age adoption passing confidence dependencies major
@biomejs/js-api (source) 3.0.0 -> 4.0.0 age adoption passing confidence devDependencies major
@biomejs/wasm-nodejs (source) 2.2.6 -> 2.3.5 age adoption passing confidence dependencies minor
@biomejs/wasm-nodejs (source) 2.2.6 -> 2.3.5 age adoption passing confidence devDependencies minor
@types/node (source) 22.16.5 -> 24.10.1 age adoption passing confidence devDependencies major
@typespec/events (source) ^0.72.1 -> ^0.76.0 age adoption passing confidence peerDependencies minor
@typespec/events (source) ^0.75.0 -> ^0.76.0 age adoption passing confidence devDependencies minor
@typespec/rest (source) ^0.72.1 -> ^0.76.0 age adoption passing confidence peerDependencies minor
@typespec/rest (source) ^0.75.0 -> ^0.76.0 age adoption passing confidence devDependencies minor
@typespec/sse (source) ^0.72.1 -> ^0.76.0 age adoption passing confidence peerDependencies minor
@typespec/sse (source) ^0.75.0 -> ^0.76.0 age adoption passing confidence devDependencies minor
@typespec/streams (source) ^0.72.1 -> ^0.76.0 age adoption passing confidence peerDependencies minor
@typespec/streams (source) ^0.75.0 -> ^0.76.0 age adoption passing confidence devDependencies minor
@typespec/versioning (source) ^0.72.1 -> ^0.76.0 age adoption passing confidence peerDependencies minor
@typespec/versioning (source) ^0.75.0 -> ^0.76.0 age adoption passing confidence devDependencies minor
@typespec/xml (source) ^0.72.1 -> ^0.76.0 age adoption passing confidence peerDependencies minor
@typespec/xml (source) ^0.75.0 -> ^0.76.0 age adoption passing confidence devDependencies minor
actions/download-artifact v5.0.0 -> v6.0.0 age adoption passing confidence action major
actions/upload-artifact v4.6.2 -> v5.0.0 age adoption passing confidence action major
koa-body ^6.0.1 -> ^7.0.0 age adoption passing confidence peerDependencies major
koa-body ^6.0.1 -> ^7.0.0 age adoption passing confidence devDependencies major
next (source) 15.5.4 -> 16.0.3 age adoption passing confidence dependencies major
node (source) 24.10.0 -> 24.11.1 age adoption passing confidence minor
pnpm (source) 10.18.3+sha512.bbd16e6d7286fd7e01f6b3c0b3c932cda2965c06a908328f74663f10a9aea51f1129eea615134bf992831b009eabe167ecb7008b597f40ff9bc75946aadfb08d -> 10.22.0 age adoption passing confidence packageManager minor
zod (source) ^3.25.74 -> ^4.0.0 age adoption passing confidence devDependencies major
zod (source) ^3.25.74 -> ^4.0.0 age adoption passing confidence dependencies major

Release Notes

Azure/typespec-azure (@​azure-tools/typespec-autorest)

v0.61.1

Bug Fixes
biomejs/biome (@​biomejs/biome)

v2.3.5

Compare Source

Patch Changes
  • #​8023 96f3e77 Thanks @​ematipico! - Added support Svelte syntax {@​html}. Biome now is able to parse and format the Svelte syntax {@​html}:

    -{@​html   'div'}
    +{@​html 'div'}

    The contents of the expressions inside the {@&#8203;html <expression>} aren't formatted yet.

  • #​8058 5f68bcc Thanks @​ematipico! - Fixed a bug where the Biome Language Server would enable its project file watcher even when no project rules were enabled.

    Now the watching of nested configuration files and nested ignore files is delegated to the editor, if their LSP spec supports it.

  • #​8023 96f3e77 Thanks @​ematipico! - Added support Svelte syntax {@&#8203;render}. Biome now is able to parse and format the Svelte syntax {@&#8203;render}:

    -{@&#8203;render   sum(1, 2)   }
    +{@&#8203;render sum(1, 2)}

    The contents of the expressions inside the {@&#8203;render <expression>} aren't formatted yet.

  • #​8006 f0612a5 Thanks @​Bertie690! - Updated documentation and diagnostic for lint/complexity/noBannedTypes. The rule should have a more detailed description and diagnostic error message.

  • #​8039 da70d8b Thanks @​PFiS1737! - Biome now keeps a blank line after the frontmatter section in Astro files.

  • #​8042 b7efa6f Thanks @​dyc3! - The CSS Parser, with tailwindDirectives enabled, will now accept at rules like @media and @supports in @custom-variant shorthand syntax.

  • #​8064 3ff9d45 Thanks @​dibashthapa! - Fixed #​7967: Fixed the issue with support for advanced SVG props

  • #​8023 96f3e77 Thanks @​ematipico! - Added support Svelte syntax {@&#8203;attach}. Biome now is able to parse and format the Svelte syntax {@&#8203;attach}:

    -<div {@&#8203;attach    myAttachment   }>...</div>
    +<div {@&#8203;attach myAttachment}>...</div>

    The contents of the expressions inside the {@&#8203;attach <expression>} aren't formatted yet.

  • #​8001 6e8a50e Thanks @​ematipico! - Added support Svelte syntax {#key}. Biome now is able to parse and format the Svelte syntax {#key}:

    -{#key   expression} <div></div> {/key}
    +{#key expression}
    +  <div></div>
    +{/key}

    The contents of the expressions inside the {#key <expression>} aren't formatted yet.

  • #​8023 96f3e77 Thanks @​ematipico! - Added support Svelte syntax {@&#8203;const}. Biome now is able to parse and format the Svelte syntax {@&#8203;const}:

    -{@&#8203;const   name = value}
    +{@&#8203;const name = value}

    The contents of the expressions inside the {@&#8203;const <expression>} aren't formatted yet.

  • #​8044 8f77d4a Thanks @​Netail! - Corrected rule source references. biome migrate eslint should do a bit better detecting rules in your eslint configurations.

  • #​8065 1a2d1af Thanks @​Netail! - Added the nursery rule useArraySortCompare. Require Array#sort and Array#toSorted calls to always provide a compareFunction.

    Invalid:

    const array = [];
    array.sort();

    Valid:

    const array = [];
    array.sort((a, b) => a - b);
  • #​7673 a3a713d Thanks @​dyc3! - The HTML parser is now able to parse vue directives. This enables us to write/port Vue lint rules that require inspecting the <template> section. However, this more complex parsing may result in parsing errors where there was none before. For those of you that have opted in to the experimental support (aka experimentalFullSupportEnabled), we greatly appreciate your help testing this out, and your bug reports.

  • #​8031 fa6798a Thanks @​ematipico! - Added support for the Svelte syntax {#if}{/if}. The Biome HTML parser is now able to parse and format the {#if}{/if} blocks:

    <!-- if / else-if / else -->
    {#if porridge.temperature > 100}
    -<p>too hot!</p>
    +  <p>too hot!</p>
    {:else if 80 > porridge.temperature}
    -<p>too cold!</p>
    +  <p>too cold!</p>
    {:else if 100 > porridge.temperature}
    -<p>too too cold!</p>
    +  <p>too too cold!</p>
    {:else}
    -<p>just right!</p>
    +  <p>just right!</p>
    {/if}
  • #​8041 beeb7bb Thanks @​dyc3! - The CSS parser, with tailwindDirectives enabled, will now accept lists of selectors in @custom-variant shorthand syntax.

    @&#8203;custom-variant cell (th:has(&), td:has(&));
  • #​8028 c09e45c Thanks @​fmajestic! - The GitLab reporter now outputs format errors.

  • #​8037 78011b1 Thanks @​PFiS1737! - indentScriptAndStyle no longer indents the frontmatter in Astro files.

  • #​8009 6374b1f Thanks @​tmcw! - Fixed an edge case in the useArrowFunction rule.

    The rule no longer emits diagnostics for or offers to fix functions that reference
    the arguments object,
    because that object is undefined for arrow functions.

    Valid example:

    // Valid: this function cannot be transformed into an arrow function because
    // arguments is not defined for arrow functions.
    const getFirstArg = function () {
      return arguments[0];
    };

v2.3.4

Compare Source

Patch Changes
  • #​7989 4855c4a Thanks @​alissonlauffer! - Fixed a regression in Astro frontmatter parsing where comments inside quoted strings were incorrectly detected as actual comments. This caused the parser to prematurely terminate frontmatter parsing when encountering strings like const test = "//";.
    For example, the following Astro frontmatter now parses correctly:

    ---
    const test = "// not a real comment";
    ---
  • #​7968 0b28f5f Thanks @​denbezrukov! - Refactored formatter to use strict Token element for better performance. The new Token variant is optimized for static, ASCII-only text (keywords, operators, punctuation) with the following constraints:

    • ASCII only (no Unicode characters)
    • No newlines (\n, \r)
    • No tab characters (\t)

    This enables faster printing and fitting logic by using bulk string operations (push_str, len()) instead of character-by-character iteration with Unicode width calculations.

  • #​7941 19b8280 Thanks @​Conaclos! - Fixed #​7943. Rules' options are now properly merged with the inherited options from a shared configuration.

    This means that you can now override a specific option from a rule without resetting the other options to their default.

    Given the following shared configuration:

    {
      "linter": {
        "rules": {
          "style": {
            "useNamingConvention": {
              "level": "on",
              "options": {
                "strictCase": false,
                "conventions": [
                  {
                    "selector": { "kind": "variable", "scope": "global" },
                    "formats": ["CONSTANT_CASE"]
                  }
                ]
              }
            }
          }
        }
      }
    }

    And the user configuration that extends this shared configuration:

    {
      "extends": ["shared.json"],
      "linter": {
        "rules": {
          "style": {
            "useNamingConvention": {
              "level": "on",
              "options": { "strictCase": true }
            }
          }
        }
      }
    }

    The obtained merged configuration is now as follows:

    {
      "extends": ["shared.json"],
      "linter": {
        "rules": {
          "style": {
            "useNamingConvention": {
              "level": "on",
              "options": {
                "strictCase": true,
                "conventions": [
                  {
                    "selector": { "kind": "variable", "scope": "global" },
                    "formats": ["CONSTANT_CASE"]
                  }
                ]
              }
            }
          }
        }
      }
    }
  • #​7969 425963d Thanks @​ematipico! - Added support for the Svelte syntax {@&#8203;debug}. The Biome HTML parser is now able to parse and format the blocks:

    -{@&#8203;debug     foo,bar,    something}
    +{@&#8203;debug foo, bar, something}
  • #​7986 3256f82 Thanks @​lisiur! - Fixed #​7981. Now Biome correctly detects and parses lang='tsx' and lang='jsx' languages when used inside in .vue files, when .experimentalFullSupportEnabled is enabled.

  • #​7921 547c2da Thanks @​dyc3! - Fixed #​7854: The CSS parser, with tailwindDirectives enabled, will now parse @source inline("underline");.

  • #​7856 c9e20c3 Thanks @​Netail! - Added the nursery rule noContinue. Disallowing the usage of the continue statement, structured control flow statements such as if should be used instead.

    Invalid:

    let sum = 0,
      i;
    
    for (i = 0; i < 10; i++) {
      if (i >= 5) {
        continue;
      }
    
      sum += i;
    }

    Valid:

    let sum = 0,
      i;
    
    for (i = 0; i < 10; i++) {
      if (i < 5) {
        sum += i;
      }
    }

v2.3.3

Compare Source

Patch Changes

v2.3.2

Compare Source

Patch Changes
  • #​7859 c600618 Thanks @​Netail! - Added the nursery rule noIncrementDecrement, disallows the usage of the unary operators ++ and --.

  • #​7901 0d17b05 Thanks @​ematipico! - Fixed #​7837, where Biome couldn't properly parse text expressions that contained nested curly brackets. This was breaking parsing in Astro and Svelte files.

  • #​7874 e617d36 Thanks @​Bertie690! - Fixed #​7230: noUselessStringConcat no longer emits false positives for multi-line strings with leading + operators.

    Previously, the rule did not check for leading newlines on the + operator, emitting false positives if one occurred at the start of a line.
    Notably, formatting with operatorLinebreak="before" would move the + operators to the start of lines automatically, resulting in spurious errors whenever a multi-line string was used.

    Now, the rule correctly detects and ignores multi-line concatenations with leading operators as well, working regardless of the setting of operatorLinebreak.

    Example

    // The following code used to error if the `+` operators were at the start of lines (as opposed to the end).
    // Now, the rule correctly recognizes this as a stylistic concatenation and ignores it.
    const reallyLongStringThatShouldNotError =
      "Lorem ipsum dolor sit amet consectetur adipiscing elit." +
      "Quisque faucibus ex sapien vitae pellentesque sem placerat." +
      "In id cursus mi pretium tellus duis convallis." +
      "Tempus leo eu aenean sed diam urna tempor. Pulvinar vivamus fringilla";
  • #​7786 33ffcd5 Thanks @​daivinhtran! - Fixed #​7601: Properly match Grit plugin's code snippet with only one child.

  • #​7901 0d17b05 Thanks @​ematipico! - Fixed #​7837, where Biome Language Server panicked when opening HTML-ish files when the experimental full support is enabled.

v2.3.1

Compare Source

Patch Changes
  • #​7840 72afdfa Thanks @​ematipico! - Fixed #​7838, which caused the new --css-parse-* arguments not being recognised by the ci command.

  • #​7789 d5b416e Thanks @​fronterior! - Fixed the LSP method workspace/didChangeWorkspaceFolders to perform incremental updates instead of replacing the entire folder list.

  • #​7852 bd254c7 Thanks @​dyc3! - Fixed #​7843: The CSS parser, when tailwindDirectives is enabled, correctly parses --*: initial;.

  • #​7872 0fe13fe Thanks @​dyc3! - Fixed #​7861: The HTML parser will now accept Svelte attribute shorthand syntax in .svelte files.

  • #​7866 7b2600b Thanks @​dyc3! - Fixed #​7860: The css parser, with tailwindDirectives enabled, will now accept @plugin options.

  • #​7853 fe90c78 Thanks @​dyc3! - Fixed #​7848: The css parser with tailwindDirectives enabled will now correctly parse tailwind's source exclude syntax: @source not "foo.css";

  • #​7878 c9f7fe5 Thanks @​ematipico! - Fixed #​7857: Biome now parses <script> tags as TypeScript when analysing .astro files.

  • #​7867 b42b718 Thanks @​smorimoto! - Fixed incorrect option name in HTML parser error message.

    The error message for disabled text expressions incorrectly referred
    to the html.parser.textExpression option, which does not exist.
    Updated it to reference the correct html.parser.interpolation option.

v2.3.0

Compare Source

Minor Changes
Example

Given the following file structure:

tsconfig.json

{
  "compilerOptions": {
    "baseUrl": "./src"
  }
}

src/foo.ts

export function foo() {}

In this scenario, import { foo } from "foo"; should work regardless of the
location of the file containing the import statement.

Fixes #​6432.

  • #​7745 6fcbc07 Thanks @​dyc3! - Added ignore option to noUnknownAtRules. If an unknown at-rule matches any of the items provided in ignore, a diagnostic won't be emitted.

  • #​7753 63cb7ff Thanks @​ematipico! - Enhanced the init command. The init command now checks if the existing project contains known ignore files and known generated folders.

    If Biome finds .gitignore or .ignore files, it will add the following configuration to biome.json:

    {
    +  "vcs": {
    +    "enabled": true,
    +    "clientKind": "git",
    +    "useIgnoreFile": true
    +  }
    }

    If Biome finds a dist/ folder, it will exclude it automatically using the double-exclude syntax:

    {
    +  "files": {
    +    "includes": ["**", "!!**/dist"]
    +  }
    }
  • #​7548 85d3a3a Thanks @​siketyan! - The rules in a domain are no longer enabled automatically by the installed dependencies unless the rule is recommended.

  • #​7723 d3aac63 Thanks @​ematipico! - Added --css-parse-css-modules CLI flag to control whether CSS Modules syntax is enabled.

    You can now enable or disable CSS Modules parsing directly from the command line:

    biome check --css-parse-css-modules=true file.module.css
    biome format --css-parse-css-modules=true file.module.css
    biome lint --css-parse-css-modules=true file.module.css
    biome ci --css-parse-css-modules=true file.module.css
  • [#​7723](https://redirect.github.com/biomejs/biome/p


Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, on day 1 of the month ( * 0-3 1 * * ) (UTC), 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.

@renovate
Copy link
Contributor Author

renovate bot commented Nov 1, 2025

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: undefined
Command failed: corepack use pnpm@10.22.0

File name: pnpm-lock.yaml
Scope: all 13 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
 ERR_PNPM_NO_MATCHING_VERSION  No matching version found for @biomejs/wasm-nodejs@2.3.5 published by Thu Nov 06 2025 23:01:51 GMT+0000 (Coordinated Universal Time) while fetching it from https://registry.npmjs.org/. Version 2.3.5 satisfies the specs but was released at Tue Nov 11 2025 12:32:55 GMT+0000 (Coordinated Universal Time)

This error happened while installing a direct dependency of /tmp/renovate/repos/github/mnahkies/openapi-code-generator

The latest release of @biomejs/wasm-nodejs is "2.3.5". Published at 11/11/2025

Other releases are:
  * nightly: 1.9.5-nightly.81fdedb published at 11/26/2024
  * beta: 2.0.0-beta.6 published at 6/2/2025

If you need the full list of all 105 published versions run "$ pnpm view @biomejs/wasm-nodejs versions".

If you want to install the matched version ignoring the time it was published, you can add the package name to the minimumReleaseAgeExclude setting. Read more about it: https://pnpm.io/settings#minimumreleaseageexclude

@renovate renovate bot force-pushed the renovate/all branch 4 times, most recently from 3856b26 to 44f9de4 Compare November 10, 2025 02:38
@renovate renovate bot force-pushed the renovate/all branch 5 times, most recently from 6bdc3d1 to 0b862b4 Compare November 13, 2025 23:01
@renovate
Copy link
Contributor Author

renovate bot commented Nov 15, 2025

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@mnahkies mnahkies enabled auto-merge (squash) November 15, 2025 14:31
@mnahkies mnahkies merged commit 96e2e83 into main Nov 15, 2025
22 checks passed
@mnahkies mnahkies deleted the renovate/all branch November 15, 2025 14:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants