Skip to content

chore(deps): update all dependencies #2051

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Jul 21, 2025
Merged

chore(deps): update all dependencies #2051

merged 1 commit into from
Jul 21, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 21, 2025

This PR contains the following updates:

Package Change Age Confidence
@biomejs/biome (source) 2.1.1 -> 2.1.2 age confidence
@types/node (source) 22.16.3 -> 22.16.5 age confidence
@vitejs/plugin-react (source) 4.6.0 -> 4.7.0 age confidence
turbo (source) 2.5.4 -> 2.5.5 age confidence

Release Notes

biomejs/biome (@​biomejs/biome)

v2.1.2

Compare Source

Patch Changes

  • #​6908 d77eaff Thanks @​ematipico! - Fix #​6485: Handle multiple semicolons correctly in blocks (#​6485)

    div {
  box-sizing: border-box;
  color: red;
}

  • #​6908 d77eaff Thanks @​ematipico! - Fixed #​6762, Biome now knows that ~/.config/zed/settings.json and ~/.config/Code/User/settings.json allows comments by default.

  • #​6908 d77eaff Thanks @​ematipico! - Refactor: remove one level of indirection for CSS declarations with semicolon
    Previously, accessing a declaration from a list required an extra step:

    item
.as_any_css_declaration_with_semicolon()
.as_css_declaration_with_semicolon()

    Now, it can be done directly with:

    item.as_css_declaration_with_semicolon()

  • #​6908 d77eaff Thanks @​ematipico! - Fixed a bug where the Biome Language Server didn't correctly ignore specific files when vcs.useIgnoreFile is set to true.

  • #​6908 d77eaff Thanks @​ematipico! - Improved the performance of noImportCycles by ~30%.

  • #​6908 d77eaff Thanks @​ematipico! - Fixed #​6829: Fixed a false positive reported by useImportExtensions when importing a .js file that had a matching .d.ts file in the same folder.

  • #​6908 d77eaff Thanks @​ematipico! - Fixed an issue where biome was using the wrong string quotes when the classes string has quotes, resulting in invalid code after applying the fix.

  • #​6908 d77eaff Thanks @​ematipico! - Improved #​6172: Optimised the way function arguments are stored in Biome's type inference. This led to about 10% performance improvement in RedisCommander.d.ts and about 2% on @next/font type definitions.

  • #​6908 d77eaff Thanks @​ematipico! - Fixed a bug where the Biome Language Server would apply an unsafe fix when using the code action quickfix.biome.

    Now Biome no longer applies an unsafe code fix when using the code action quickfix.biome.

  • #​6908 d77eaff Thanks @​ematipico! - Fixed #​6719: The noInvalidUseBeforeDeclaration rule covers additional use cases.

    Examples:

    type Bar = { [BAR]: true };
const BAR = "bar";
    interface Bar {
  child: { grandChild: { [BAR]: typeof BAR; enumFoo: EnumFoo } };
}
const BAR = "bar";
enum EnumFoo {
  BAR = "bar",
}

  • #​6908 d77eaff Thanks @​ematipico! - Biome now considers whether the linter is enabled when figuring out how the project should be scanned. Resolves #​6815.

  • #​6908 d77eaff Thanks @​ematipico! - Fixed #​6165: Fixed false negative in noUnusedPrivateClassMembers rule when checking member usage in classes

  • #​6908 d77eaff Thanks @​ematipico! - Fixed a bug where the root ignore file wasn't correctly loaded during the scanning phase, causing false positives and incorrect expectations among users.

    Now, when using vcs.useIgnoreFile, the the globs specified in the ignore file from the project root will have the same semantics as the files.includes setting of the root configuration.

    Refer to the relative web page to understand how they work.

  • #​6908 d77eaff Thanks @​ematipico! - Fixed #​6891: Improved type inference for array indices.

    Example:

    const numbers: number[];
numbers[42]; // This now infers to `number | undefined`.

  • #​6908 d77eaff Thanks @​ematipico! - Fixed #​6796: Fixed a false positive that happened in noFloatingPromises when calling functions that were declared as part of for ... of syntax inside async functions.

    Instead, the variables declared inside for ... of loops are now correctly
    inferred if the expression being iterated evaluates to an Array (support for other iterables will follow later).

    Invalid example

    const txStatements: Array<(tx) => Promise<any>> = [];

db.transaction((tx: any) => {
  for (const stmt of txStatements) {
    // We correctly flag this resolves to a `Promise`:
    stmt(tx);
  }
});

    Valid example

    async function valid(db) {
  const txStatements: Array<(tx: any) => void> = [(tx) => tx.insert().run()];

  db.transaction((tx: any) => {
    for (const stmt of txStatements) {
      // We don't flag a false positive here anymore:
      stmt(tx);
    }
  });
}

  • #​6908 d77eaff Thanks @​ematipico! - Added the rule noVueReservedProps, resolves #​6309.

    It prevents the use of reserved Vue prop names such as key and ref which can cause conflicts and unexpected behavior in Vue components.

    Invalid example
    import { defineComponent } from "vue";

export default defineComponent({
  props: ["ref", "key", "foo"],
});
    <script setup>
defineProps({
  ref: String,
  key: String,
  foo: String,
});
</script>
    Valid examples
    import { defineComponent } from "vue";

export default defineComponent({
  props: ["foo"],
});
    <script setup>
defineProps({ foo: String });
</script>

  • #​6912 af7c6c0 Thanks @​ematipico! - Fixed #​6904. Now Biome correctly applies the argument --assist-enabled=false when running the command ci and the command check.

  • #​6908 d77eaff Thanks @​ematipico! - Allow multiple identifiers in ::part() pseudo-element selector.

    ::part(first second) {
}

  • #​6908 d77eaff Thanks @​ematipico! - Fixed #​6510: The scanner no longer shows diagnostics on inaccessible files unless --verbose is used.

  • #​6908 d77eaff Thanks @​ematipico! - Fixed #​6837: Fixed regression with multiple consecutive line suppression comments using instances (like // biome-ignore lint/correctness/useExhaustiveDependencies(depName): reason).

  • #​6908 d77eaff Thanks @​ematipico! - Fixed an issue where textDocument/codeAction in the LSP could respond with outdated text edits after the workspace watcher observed outdated changes to the file.

  • #​6908 d77eaff Thanks @​ematipico! - noFloatingPromises will no longer suggest to add await keyword inside synchronous callbacks nested inside async functions.

  • #​6908 d77eaff Thanks @​ematipico! - Fixed #​6777: Fixed type inference handling of this to avoid infinite recursion.

    Thanks to @​sterliakov for the thorough investigation!

  • #​6908 d77eaff Thanks @​ematipico! - Fixed #​6775: useReadonlyClassProperties now also captures mutations inside function arguments.

    Example:

    class Counter {
  private counter: number;
  count() {
    console.log(this.counter++);
    const counterString = `${this.counter++}`;
  }
}

  • #​6723 c434f01 Thanks @​sterliakov! - useUniqueElementIds now has an excludedComponents option to support elements using id prop for reasons not related to DOM element id. Fixed #​6722.

  • #​6908 d77eaff Thanks @​ematipico! - Fixed a bug where Biome didn't throw any error when vcs.useIgnoreFile is set to true, and there wasn't any ignore file read. Now Biome correctly throws an error if no ignore files are found.

  • #​6911 6d68074 Thanks @​arendjr! - Fixed #​6838: Reduce resource consumption in the Biome Language Server by using non-recursive filesystem watchers instead of recursive ones.

    Watchers are responsible for notifying Biome of changes to files in the filesystem. We used to set up a single recursive watcher, but that meant that Biome would receive filesystem notifications for all files in your project, even for ignored folders such as build/ or dist/ folders.

    With this patch, we set up non-recursive watchers only for the folders that are relevant to a project.

    Related to this, we also solved an issue where incoming notifications were incorrectly filtered, causing ignored files to be processed and stored in our module graph anyway.

vitejs/vite-plugin-react (@​vitejs/plugin-react)

v4.7.0

Compare Source

Add HMR support for compound components (#​518)

HMR now works for compound components like this:

const Root = () => <div>Accordion Root</div>
const Item = () => <div>Accordion Item</div>

export const Accordion = { Root, Item }
Return Plugin[] instead of PluginOption[] (#​537)

The return type has changed from react(): PluginOption[] to more specialized type react(): Plugin[]. This allows for type-safe manipulation of plugins, for example:

// previously this causes type errors
react({ babel: { plugins: ['babel-plugin-react-compiler'] } })
  .map(p => ({ ...p, applyToEnvironment: e => e.name === 'client' }))
vercel/turborepo (turbo)

v2.5.5: Turborepo v2.5.5

Compare Source

What's Changed

Docs
Examples
Changelog

New Contributors

Full Changelog: vercel/turborepo@v2.5.4...v2.5.5

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: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.

@changeset-bot changeset-bot
Copy link

changeset-bot bot commented Jul 21, 2025

⚠️ No Changeset found

Latest commit: 6183967

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@socket-security Socket Security
Copy link

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security		 Vulnerability Quality Maintenance License
Updatedturbo@​2.5.4 ⏵ 2.5.5100 +110085 +197 +1100
Updated@​biomejs/​biome@​2.1.1 ⏵ 2.1.2100 +110010099 +2100

View full report

@codecov Codecov
Copy link

codecov bot commented Jul 21, 2025 •
edited
Loading

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.29%. Comparing base (667b328) to head (6183967).
Report is 1 commits behind head on main.

✅ All tests successful. No failed tests found.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #2051      +/-   ##
==========================================
- Coverage   90.69%   90.29%   -0.40%     
==========================================
  Files          94       94              
  Lines        3825     3823       -2     
  Branches      564      566       +2     
==========================================
- Hits         3469     3452      -17     
- Misses        346      359      +13     
- Partials       10       12       +2

see 4 files with indirect coverage changes

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@renovate renovate bot merged commit aabdacd into main Jul 21, 2025
10 checks passed
@renovate renovate bot deleted the renovate/all branch July 21, 2025 04:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@renovate-approve renovate-approve[bot] renovate-approve[bot] approved these changes

Assignees
No one assigned
Labels
🤖 Dependencies
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants