Skip to content

chore(deps): update all patch dependencies - #6310

Merged
chenjiahan merged 1 commit into
mainfrom
renovate/all-patch
Oct 6, 2025
Merged

chore(deps): update all patch dependencies#6310
chenjiahan merged 1 commit into
mainfrom
renovate/all-patch

Conversation

@renovate

@renovate renovate Bot commented Oct 6, 2025

Copy link
Copy Markdown
Contributor

Note

Mend has cancelled the proposed renaming of the Renovate GitHub app being renamed to mend[bot].

This notice will be removed on 2025-10-07.


This PR contains the following updates:

Package Change Age Confidence
@biomejs/biome (source) ^2.2.4 -> ^2.2.5 age confidence
@prefresh/core (source) ^1.5.7 -> ^1.5.8 age confidence
@rsbuild/core (source) ^1.5.12 -> ^1.5.13 age confidence
@rstest/core (source) ^0.5.0 -> ^0.5.1 age confidence
@tailwindcss/postcss (source) ^4.1.13 -> ^4.1.14 age confidence
@types/node (source) ^22.18.6 -> ^22.18.8 age confidence
@typescript/native-preview (source) 7.0.0-dev.20250928.1 -> 7.0.0-dev.20251005.1 age confidence
jiti ^2.6.0 -> ^2.6.1 age confidence
nx (source) ^21.6.2 -> ^21.6.3 age confidence
svelte (source) ^5.39.6 -> ^5.39.9 age confidence
tailwindcss (source) ^4.1.13 -> ^4.1.14 age confidence
typescript (source) ^5.9.2 -> ^5.9.3 age confidence

Release Notes

biomejs/biome (@​biomejs/biome)

v2.2.5

Compare Source

Patch Changes
  • #​7597 5c3d542 Thanks @​arendjr! - Fixed #​6432: useImportExtensions now works correctly with aliased paths.

  • #​7269 f18dac1 Thanks @​CDGardner! - Fixed #​6648, where Biome's noUselessFragments contained inconsistencies with ESLint for fragments only containing text.

    Previously, Biome would report that fragments with only text were unnecessary under the noUselessFragments rule. Further analysis of ESLint's behavior towards these cases revealed that text-only fragments (<>A</a>, <React.Fragment>B</React.Fragment>, <RenamedFragment>B</RenamedFragment>) would not have noUselessFragments emitted for them.

    On the Biome side, instances such as these would emit noUselessFragments, and applying the suggested fix would turn the text content into a proper JS string.

    // Ended up as: - const t = "Text"
    const t = <>Text</>
    
    // Ended up as: - const e = t ? "Option A" : "Option B"
    const e = t ? <>Option A</> : <>Option B</>
    
    /* Ended up as:
      function someFunc() {
        return "Content desired to be a multi-line block of text."
      }
    */
    function someFunc() {
      return <>
        Content desired to be a multi-line
        block of text.
      <>
    }

    The proposed update was to align Biome's reaction to this rule with ESLint's; the aforementioned examples will now be supported from Biome's perspective, thus valid use of fragments.

    // These instances are now valid and won't be called out by noUselessFragments.
    
    const t = <>Text</>
    const e = t ? <>Option A</> : <>Option B</>
    
    function someFunc() {
      return <>
        Content desired to be a multi-line
        block of text.
      <>
    }
  • #​7498 002cded Thanks @​siketyan! - Fixed #​6893: The useExhaustiveDependencies rule now correctly adds a dependency that is captured in a shorthand object member. For example:

    useEffect(() => {
      console.log({ firstId, secondId });
    }, []);

    is now correctly fixed to:

    useEffect(() => {
      console.log({ firstId, secondId });
    }, [firstId, secondId]);
  • #​7509 1b61631 Thanks @​siketyan! - Added a new lint rule noReactForwardRef, which detects usages of forwardRef that is no longer needed and deprecated in React 19.

    For example:

    export const Component = forwardRef(function Component(props, ref) {
      return <div ref={ref} />;
    });

    will be fixed to:

    export const Component = function Component({ ref, ...props }) {
      return <div ref={ref} />;
    };

    Note that the rule provides an unsafe fix, which may break the code. Don't forget to review the code after applying the fix.

  • #​7520 3f06e19 Thanks @​arendjr! - Added new nursery rule noDeprecatedImports to flag imports of deprecated symbols.

Invalid example
// foo.js
import { oldUtility } from "./utils.js";
// utils.js
/**
 * @&#8203;deprecated
 */
export function oldUtility() {}
Valid examples
// foo.js
import { newUtility, oldUtility } from "./utils.js";
// utils.js
export function newUtility() {}

// @&#8203;deprecated (this is not a JSDoc comment)
export function oldUtility() {}
  • #​7457 9637f93 Thanks @​kedevked! - Added style and requireForObjectLiteral options to the lint rule useConsistentArrowReturn.

    This rule enforces a consistent return style for arrow functions. It can be configured with the following options:

    • style: (default: asNeeded)
      • always: enforces that arrow functions always have a block body.
      • never: enforces that arrow functions never have a block body, when possible.
      • asNeeded: enforces that arrow functions have a block body only when necessary (e.g. for object literals).
style: "always"

Invalid:

const f = () => 1;

Valid:

const f = () => {
  return 1;
};
style: "never"

Invalid:

const f = () => {
  return 1;
};

Valid:

const f = () => 1;
style: "asNeeded"

Invalid:

const f = () => {
  return 1;
};

Valid:

const f = () => 1;
style: "asNeeded" and requireForObjectLiteral: true

Valid:

const f = () => {
  return { a: 1 };
};
  • #​7510 527cec2 Thanks @​rriski! - Implements #​7339. GritQL patterns can now use native Biome AST nodes using their PascalCase names, in addition to the existing TreeSitter-compatible snake_case names.

    engine biome(1.0)
    language js(typescript,jsx)
    
    or {
      // TreeSitter-compatible pattern
      if_statement(),
    
      // Native Biome AST node pattern
      JsIfStatement()
    } as $stmt where {
      register_diagnostic(
        span=$stmt,
        message="Found an if statement"
      )
    }
    
  • #​7574 47907e7 Thanks @​kedevked! - Fixed 7574. The diagnostic message for the rule useSolidForComponent now correctly emphasizes <For /> and provides a working hyperlink to the Solid documentation.

  • #​7497 bd70f40 Thanks @​siketyan! - Fixed #​7320: The useConsistentCurlyBraces rule now correctly detects a string literal including " inside a JSX attribute value.

  • #​7522 1af9931 Thanks @​Netail! - Added extra references to external rules to improve migration for the following rules: noUselessFragments & noNestedComponentDefinitions

  • #​7597 5c3d542 Thanks @​arendjr! - Fixed an issue where package.json manifests would not be correctly discovered
    when evaluating files in the same directory.

  • #​7565 38d2098 Thanks @​siketyan! - The resolver can now correctly resolve .ts, .tsx, .d.ts, .js files by .js extension if exists, based on the file extension substitution in TypeScript.

    For example, the linter can now detect the floating promise in the following situation, if you have enabled the noFloatingPromises rule.

    foo.ts

    export async function doSomething(): Promise<void> {}

    bar.ts

    import { doSomething } from "./foo.js"; // doesn't exist actually, but it is resolved to `foo.ts`
    
    doSomething(); // floating promise!
  • #​7542 cadad2c Thanks @​mdevils! - Added the rule noVueDuplicateKeys, which prevents duplicate keys in Vue component definitions.

    This rule prevents the use of duplicate keys across different Vue component options such as props, data, computed, methods, and setup. Even if keys don't conflict in the script tag, they may cause issues in the template since Vue allows direct access to these keys.

    Invalid examples
    <script>
    export default {
      props: ["foo"],
      data() {
        return {
          foo: "bar",
        };
      },
    };
    </script>
    <script>
    export default {
      data() {
        return {
          message: "hello",
        };
      },
      methods: {
        message() {
          console.log("duplicate key");
        },
      },
    };
    </script>
    <script>
    export default {
      computed: {
        count() {
          return this.value * 2;
        },
      },
      methods: {
        count() {
          this.value++;
        },
      },
    };
    </script>
    Valid examples
    <script>
    export default {
      props: ["foo"],
      data() {
        return {
          bar: "baz",
        };
      },
      methods: {
        handleClick() {
          console.log("unique key");
        },
      },
    };
    </script>
    <script>
    export default {
      computed: {
        displayMessage() {
          return this.message.toUpperCase();
        },
      },
      methods: {
        clearMessage() {
          this.message = "";
        },
      },
    };
    </script>
  • #​7546 a683acc Thanks @​siketyan! - Internal data for Unicode strings have been updated to Unicode 17.0.

  • #​7497 bd70f40 Thanks @​siketyan! - Fixed #​7256: The useConsistentCurlyBraces rule now correctly ignores a string literal with braces that contains only whitespaces. Previously, literals that contains single whitespace were only allowed.

  • #​7565 38d2098 Thanks @​siketyan! - The useImportExtensions rule now correctly detects imports with an invalid extension. For example, importing .ts file with .js extension is flagged by default. If you are using TypeScript with neither the allowImportingTsExtensions option nor the rewriteRelativeImportExtensions option, it's recommended to turn on the forceJsExtensions option of the rule.

  • #​7581 8653921 Thanks @​lucasweng! - Fixed #​7470: solved a false positive for noDuplicateProperties. Previously, declarations in @container and @starting-style at-rules were incorrectly flagged as duplicates of identical declarations at the root selector.

    For example, the linter no longer flags the display declaration in @container or the opacity declaration in @starting-style.

    a {
      display: block;
      @&#8203;container (min-width: 600px) {
        display: none;
      }
    }
    
    [popover]:popover-open {
      opacity: 1;
      @&#8203;starting-style {
        opacity: 0;
      }
    }
  • #​7529 fea905f Thanks @​qraqras! - Fixed #​7517: the useOptionalChain rule no longer suggests changes for typeof checks on global objects.

    // ok
    typeof window !== "undefined" && window.location;
  • #​7476 c015765 Thanks @​ematipico! - Fixed a bug where the suppression action for noPositiveTabindex didn't place the suppression comment in the correct position.

  • #​7511 a0039fd Thanks @​arendjr! - Added nursery rule noUnusedExpressions to flag expressions used as a statement that is neither an assignment nor a function call.

Invalid examples
f; // intended to call `f()` instead
function foo() {
  0; // intended to `return 0` instead
}
Valid examples
f();
function foo() {
  return 0;
}
preactjs/prefresh (@​prefresh/core)

v1.5.8

Compare Source

Patch Changes
web-infra-dev/rsbuild (@​rsbuild/core)

v1.5.13

Compare Source

Highlights 💡
Browser logs

Rsbuild now forwards browser errors to your terminal — giving your coding agent more context 🤖.

image

This can be disabled via dev.browserLogs config:

export default {
  dev: {
    browserLogs: false,
  },
}
What's Changed
New Features 🎉
Performance 🚀
Bug Fixes 🐞
Refactor 🔨
Document 📖
Other Changes

Full Changelog: v1.5.12...v1.5.13

web-infra-dev/rstest (@​rstest/core)

v0.5.1

Compare Source

What's Changed

New Features 🎉
Bug Fixes 🐞
Document 📖
Other Changes

Full Changelog: web-infra-dev/rstest@v0.5.0...v0.5.1

tailwindlabs/tailwindcss (@​tailwindcss/postcss)

v4.1.14

Compare Source

Fixed
  • Handle ' syntax in ClojureScript when extracting classes (#​18888)
  • Handle @variant inside @custom-variant (#​18885)
  • Merge suggestions when using @utility (#​18900)
  • Ensure that file system watchers created when using the CLI are always cleaned up (#​18905)
  • Do not generate grid-column utilities when configuring grid-column-start or grid-column-end (#​18907)
  • Do not generate grid-row utilities when configuring grid-row-start or grid-row-end (#​18907)
  • Prevent duplicate CSS when overwriting a static utility with a theme key (#​18056)
  • Show Lightning CSS warnings (if any) when optimizing/minifying (#​18918)
  • Use default export condition for @tailwindcss/vite (#​18948)
  • Re-throw errors from PostCSS nodes (#​18373)
  • Detect classes in markdown inline directives (#​18967)
  • Ensure files with only @theme produce no output when built (#​18979)
  • Support Maud templates when extracting classes (#​18988)
  • Upgrade: Do not migrate variant = 'outline' during upgrades (#​18922)
  • Upgrade: Show version mismatch (if any) when running upgrade tool (#​19028)
  • Upgrade: Ensure first class inside className is migrated (#​19031)
  • Upgrade: Migrate classes inside *ClassName and *Class attributes (#​19031)
microsoft/typescript-go (@​typescript/native-preview)

v7.0.0-dev.20251005.1

Compare Source

v7.0.0-dev.20251004.1

Compare Source

v7.0.0-dev.20251003.1

Compare Source

v7.0.0-dev.20251002.1

Compare Source

v7.0.0-dev.20251001.1

Compare Source

v7.0.0-dev.20250930.1

Compare Source

v7.0.0-dev.20250929.1

Compare Source

unjs/jiti (jiti)

v2.6.1

Compare Source

compare changes

🩹 Fixes
  • interop: Only passthrough default if it is not a promise (#​408)
📦 Build
  • Revert to terser-webpack-plugin (#​407)
🏡 Chore
❤️ Contributors
nrwl/nx (nx)

v21.6.3

Compare Source

21.6.3 (2025-10-02)

🩹 Fixes
  • core: improve provenance error with custom registry information (#​32903)
  • core: optimize task hashing with BFS and performance logging (#​32911)
  • core: tweak configure-ai-agents prompt (#​32914)
  • core: ensure nx is published with the correct dependency version for the native packages (#​32928, #​32898)
  • js: temporarily hash all external dependencies for tasks inferred by the @nx/js/typescript plugin (#​32912)
  • nx-dev: improve default zoom level of graph nodes in docs (#​32910)
  • nx-dev: provide message to check previous docs w/ empty migrations (#​32919)
  • nx-dev: watch for theme changes for project/task graph components (#​32885)
  • nx-dev: update credit pricing link to new docs page (#​32899)
❤️ Thank You
sveltejs/svelte (svelte)

v5.39.9

Compare Source

Patch Changes
  • fix: flush when pending boundaries resolve (#​16897)

v5.39.8

Compare Source

Patch Changes
  • fix: check boundary pending attribute at runtime on server (#​16855)

  • fix: preserve tuple type in $state.snapshot (#​16864)

  • fix: allow await in svelte:boundary without pending (#​16857)

  • fix: update bind:checked error message to clarify usage with radio inputs (#​16874)

v5.39.7

Compare Source

Patch Changes
  • chore: simplify batch logic (#​16847)

  • fix: rebase pending batches when other batches are committed (#​16866)

  • fix: wrap async children in $$renderer.async (#​16862)

  • fix: silence label warning for buttons and anchor tags with title attributes (#​16872)

  • fix: coerce nullish <title> to empty string (#​16863)

microsoft/TypeScript (typescript)

v5.9.3

Compare Source


Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 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.

@netlify

netlify Bot commented Oct 6, 2025

Copy link
Copy Markdown

Deploy Preview for rsbuild ready!

Name Link
🔨 Latest commit 12fc1f4
🔍 Latest deploy log https://app.netlify.com/projects/rsbuild/deploys/68e31f4665a55b0008d63302
😎 Deploy Preview https://deploy-preview-6310--rsbuild.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 64 (🔴 down 7 from production)
Accessibility: 97 (no change from production)
Best Practices: 100 (no change from production)
SEO: 100 (no change from production)
PWA: 60 (no change from production)
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

@chenjiahan
chenjiahan merged commit 94a84cc into main Oct 6, 2025
12 checks passed
@chenjiahan
chenjiahan deleted the renovate/all-patch branch October 6, 2025 08:58
@chenjiahan chenjiahan mentioned this pull request Oct 8, 2025
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.

1 participant