Skip to content

fix(deps): update all non-major dependencies #465

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
sapphi-red merged 1 commit into from
Apr 25, 2025
Merged

fix(deps): update all non-major dependencies #465

sapphi-red merged 1 commit into from
Apr 25, 2025

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Apr 21, 2025 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@eslint/js (source) ^9.24.0 -> ^9.25.1 age adoption passing confidence
@playwright/test (source) ^1.51.1 -> ^1.52.0 age adoption passing confidence
@swc/core (source) ^1.11.21 -> ^1.11.22 age adoption passing confidence
@types/node (source) ^22.14.1 -> ^22.15.2 age adoption passing confidence
babel-plugin-react-compiler (source) 19.0.0-beta-ebf51a3-20250411 -> 19.1.0-rc.1 age adoption passing confidence
esbuild ^0.25.2 -> ^0.25.3 age adoption passing confidence
eslint (source) ^9.24.0 -> ^9.25.1 age adoption passing confidence
eslint-plugin-import-x ^4.10.3 -> ^4.11.0 age adoption passing confidence
playwright-chromium (source) ^1.51.1 -> ^1.52.0 age adoption passing confidence
pnpm (source) 10.8.1 -> 10.9.0 age adoption passing confidence
react-compiler-runtime (source) 19.0.0-beta-ebf51a3-20250411 -> 19.1.0-rc.1 age adoption passing confidence
react-router-dom (source) ^7.5.0 -> ^7.5.2 age adoption passing confidence
simple-git-hooks ^2.12.1 -> ^2.13.0 age adoption passing confidence
typescript-eslint (source) ^8.30.1 -> ^8.31.0 age adoption passing confidence
vite (source) ^6.3.0-beta.6 -> ^6.3.5 age adoption passing confidence
vite (source) ^6.2.6 -> ^6.3.3 age adoption passing confidence
vitest (source) ^3.1.1 -> ^3.1.2 age adoption passing confidence

Release Notes

eslint/eslint (@​eslint/js)

v9.25.1

Compare Source

v9.25.0

Compare Source

microsoft/playwright (@​playwright/test)

v1.52.0

Compare Source

swc-project/swc (@​swc/core)

v1.11.22

Compare Source

Bug Fixes
Features

  • (bindings/core) Enhance existing parse function to accept both string and buffer types(#​10371) (c9a2afc)

  • (css/prefixer) Fix default implementation (#​10351) (34f4e41)

Miscellaneous Tasks
Performance
Refactor
Testing
facebook/react (babel-plugin-react-compiler)

v19.1.0-rc.1

Compare Source

evanw/esbuild (esbuild)

v0.25.3

Compare Source

  • Fix lowered async arrow functions before super() (#​4141, #​4142)

    This change makes it possible to call an async arrow function in a constructor before calling super() when targeting environments without async support, as long as the function body doesn't reference this. Here's an example (notice the change from this to null):

    // Original code
class Foo extends Object {
  constructor() {
    (async () => await foo())()
    super()
  }
}

// Old output (with --target=es2016)
class Foo extends Object {
  constructor() {
    (() => __async(this, null, function* () {
      return yield foo();
    }))();
    super();
  }
}

// New output (with --target=es2016)
class Foo extends Object {
  constructor() {
    (() => __async(null, null, function* () {
      return yield foo();
    }))();
    super();
  }
}

    Some background: Arrow functions with the async keyword are transformed into generator functions for older language targets such as --target=es2016. Since arrow functions capture this, the generated code forwards this into the body of the generator function. However, JavaScript class syntax forbids using this in a constructor before calling super(), and this forwarding was problematic since previously happened even when the function body doesn't use this. Starting with this release, esbuild will now only forward this if it's used within the function body.

    This fix was contributed by @​magic-akari.

  • Fix memory leak with --watch=true (#​4131, #​4132)

    This release fixes a memory leak with esbuild when --watch=true is used instead of --watch. Previously using --watch=true caused esbuild to continue to use more and more memory for every rebuild, but --watch=true should now behave like --watch and not leak memory.

    This bug happened because esbuild disables the garbage collector when it's not run as a long-lived process for extra speed, but esbuild's checks for which arguments cause esbuild to be a long-lived process weren't updated for the new --watch=true style of boolean command-line flags. This has been an issue since this boolean flag syntax was added in version 0.14.24 in 2022. These checks are unfortunately separate from the regular argument parser because of how esbuild's internals are organized (the command-line interface is exposed as a separate Go API so you can build your own custom esbuild CLI).

    This fix was contributed by @​mxschmitt.

  • More concise output for repeated legal comments (#​4139)

    Some libraries have many files and also use the same legal comment text in all files. Previously esbuild would copy each legal comment to the output file. Starting with this release, legal comments duplicated across separate files will now be grouped in the output file by unique comment content.

  • Allow a custom host with the development server (#​4110)

    With this release, you can now use a custom non-IP host with esbuild's local development server (either with --serve= for the CLI or with the serve() call for the API). This was previously possible, but was intentionally broken in version 0.25.0 to fix a security issue. This change adds the functionality back except that it's now opt-in and only for a single domain name that you provide.

    For example, if you add a mapping in your /etc/hosts file from local.example.com to 127.0.0.1 and then use esbuild --serve=local.example.com:8000, you will now be able to visit http://local.example.com:8000/ in your browser and successfully connect to esbuild's development server (doing that would previously have been blocked by the browser). This should also work with HTTPS if it's enabled (see esbuild's documentation for how to do that).

  • Add a limit to CSS nesting expansion (#​4114)

    With this release, esbuild will now fail with an error if there is too much CSS nesting expansion. This can happen when nested CSS is converted to CSS without nesting for older browsers as expanding CSS nesting is inherently exponential due to the resulting combinatorial explosion. The expansion limit is currently hard-coded and cannot be changed, but is extremely unlikely to trigger for real code. It exists to prevent esbuild from using too much time and/or memory. Here's an example:

    a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{color:red}}}}}}}}}}}}}}}}}}}}

    Previously, transforming this file with --target=safari1 took 5 seconds and generated 40mb of CSS. Trying to do that will now generate the following error instead:

    ✘ [ERROR] CSS nesting is causing too much expansion

    example.css:1:60:
      1 │ a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{color:red}}}}}}}}}}}}}}}}}}}}
        ╵                                                             ^

  CSS nesting expansion was terminated because a rule was generated with 65536 selectors. This limit
  exists to prevent esbuild from using too much time and/or memory. Please change your CSS to use
  fewer levels of nesting.

  • Fix path resolution edge case (#​4144)

    This fixes an edge case where esbuild's path resolution algorithm could deviate from node's path resolution algorithm. It involves a confusing situation where a directory shares the same file name as a file (but without the file extension). See the linked issue for specific details. This appears to be a case where esbuild is correctly following node's published resolution algorithm but where node itself is doing something different. Specifically the step LOAD_AS_FILE appears to be skipped when the input ends with ... This release changes esbuild's behavior for this edge case to match node's behavior.

  • Update Go from 1.23.7 to 1.23.8 (#​4133, #​4134)

    This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain reports from vulnerability scanners that detect which version of the Go compiler esbuild uses, such as for CVE-2025-22871.

    As a reminder, esbuild's development server is intended for development, not for production, so I do not consider most networking-related vulnerabilities in Go to be vulnerabilities in esbuild. Please do not use esbuild's development server in production.

eslint/eslint (eslint)

v9.25.1

Compare Source

v9.25.0

Compare Source

un-ts/eslint-plugin-import-x (eslint-plugin-import-x)

v4.11.0

Compare Source

Minor Changes

v4.10.6

Compare Source

Patch Changes

v4.10.5

Compare Source

Patch Changes

v4.10.4

Compare Source

Patch Changes
pnpm/pnpm (pnpm)

v10.9.0

Compare Source

Minor Changes

  • Added support for installing JSR packages. You can now install JSR packages using the following syntax:

    pnpm add jsr:<pkg_name>

    or with a version range:

    pnpm add jsr:<pkg_name>@&#8203;<range>

    For example, running:

    pnpm add jsr:@&#8203;foo/bar

    will add the following entry to your package.json:

    {
  "dependencies": {
    "@&#8203;foo/bar": "jsr:^0.1.2"
  }
}

    When publishing, this entry will be transformed into a format compatible with npm, older versions of Yarn, and previous pnpm versions:

    {
  "dependencies": {
    "@&#8203;foo/bar": "npm:@&#8203;jsr/foo__bar@^0.1.2"
  }
}

    Related issue: #​8941.

    Note: The @jsr scope defaults to https://npm.jsr.io/ if the @jsr:registry setting is not defined.

  • Added a new setting, dangerouslyAllowAllBuilds, for automatically running any scripts of dependencies without the need to approve any builds. It was already possible to allow all builds by adding this to pnpm-workspace.yaml:

    neverBuiltDependencies: []

    dangerouslyAllowAllBuilds has the same effect but also allows to be set globally via:

    pnpm config set dangerouslyAllowAllBuilds true

    It can also be set when running a command:

    pnpm install --dangerously-allow-all-builds
Patch Changes
  • Fix a false negative in verifyDepsBeforeRun when nodeLinker is hoisted and there is a workspace package without dependencies and node_modules directory #​9424.
  • Explicitly drop verifyDepsBeforeRun support for nodeLinker: pnp. Combining verifyDepsBeforeRun and nodeLinker: pnp will now print a warning.
facebook/react (react-compiler-runtime)

v19.1.0-rc.1

Compare Source

remix-run/react-router (react-router-dom)

v7.5.2

Compare Source

Patch Changes
  • Updated dependencies:
    • react-router@7.5.2

v7.5.1

Compare Source

Patch Changes
  • Updated dependencies:
    • react-router@7.5.1
toplenboren/simple-git-hooks (simple-git-hooks)

v2.13.0

Compare Source

Minor Changes
typescript-eslint/typescript-eslint (typescript-eslint)

v8.31.0

Compare Source

🩹 Fixes
  • typescript-eslint: gracefully handle invalid flat config objects in config helper (#​11070)
  • typescript-eslint: address bugs in config() around global ignores (#​11065)
❤️ Thank You

You can read about our versioning strategy and releases on our website.

vitejs/rolldown-vite (vite)

v6.3.5

Compare Source

v6.3.4

Compare Source

v6.3.3

Compare Source

v6.3.2

Compare Source

v6.3.1

Compare Source

v6.3.0

Compare Source

v6.3.0-beta.8

Compare Source

v6.3.0-beta.7

Compare Source

vitejs/vite (vite)

v6.3.3

Compare Source

v6.3.2

Compare Source

v6.3.1

Compare Source

v6.3.0

Compare Source

vitest-dev/vitest (vitest)

v3.1.2

Compare Source

   🚀 Features
   🐞 Bug Fixes

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.

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 12 times, most recently from 7c75521 to b3d7412 Compare April 25, 2025 06:10
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from b3d7412 to 1e745e3 Compare April 25, 2025 13:03
sapphi-red
sapphi-red reviewed Apr 25, 2025
View reviewed changes
playground/compiler-react-18/package.json
"dependencies": {
"react": "^18.3.1",
"react-compiler-runtime": "19.0.0-beta-ebf51a3-20250411",
"react-compiler-runtime": "19.1.0-rc.1",
Copy link
Member

@sapphi-red sapphi-red Apr 25, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

vite-plugin-react/.github/renovate.json5

Lines 17 to 23 in ec1dfb3

{
"matchPackageNames": [
"react-compiler-runtime",
"babel-plugin-react-compiler",
],
"followTag": "latest",
},

this worked 👍

@sapphi-red sapphi-red merged commit 5d1fffd into main Apr 25, 2025
11 checks passed
@sapphi-red sapphi-red deleted the renovate/all-minor-patch branch April 25, 2025 13:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@sapphi-red sapphi-red sapphi-red left review comments

Assignees

No one assigned

Labels

dependencies

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@sapphi-red