Skip to content

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

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 2 commits into from
Aug 4, 2025
Merged

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

merged 2 commits into from
Aug 4, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 4, 2025

This PR contains the following updates:

Package Change Age Confidence
@cloudflare/vite-plugin (source) ^1.10.1 -> ^1.11.0 age confidence
@playwright/test (source) ^1.54.1 -> ^1.54.2 age confidence
@rolldown/pluginutils (source) 1.0.0-beta.29 -> 1.0.0-beta.30 age confidence
@types/node (source) ^22.16.5 -> ^22.17.0 age confidence
@types/react (source) ^19.1.8 -> ^19.1.9 age confidence
@types/react-dom (source) ^19.1.6 -> ^19.1.7 age confidence
eslint-plugin-n ^17.21.2 -> ^17.21.3 age confidence
eslint-plugin-regexp ^2.9.0 -> ^2.9.1 age confidence
playwright-chromium (source) ^1.54.1 -> ^1.54.2 age confidence
pnpm (source) 10.13.1 -> 10.14.0 age confidence
react (source) ^19.1.0 -> ^19.1.1 age confidence
react-dom (source) ^19.1.0 -> ^19.1.1 age confidence
react-is (source) ^19.1.0 -> ^19.1.1 age confidence
react-server-dom-webpack (source) ^19.1.0 -> ^19.1.1 age confidence
rolldown (source) 1.0.0-beta.29 -> 1.0.0-beta.30 age confidence
simple-git-hooks ^2.13.0 -> ^2.13.1 age confidence
tsdown ^0.13.0 -> ^0.13.2 age confidence
typescript (source) ^5.8.3 -> ^5.9.2 age confidence
vite (source) ^7.0.11 -> ^7.0.12 age confidence
wrangler (source) ^4.26.0 -> ^4.27.0 age confidence

Release Notes

cloudflare/workers-sdk (@​cloudflare/vite-plugin)

v1.11.0

Compare Source

Minor Changes

  • #​9914 a24c9d8 Thanks @​petebacondarwin! - Add support for loading local dev vars from .env files

    If there are no .dev.vars or .dev.vars.<environment> files, when running Wrangler or the Vite plugin in local development mode,
    they will now try to load additional local dev vars from .env, .env.local, .env.<environment> and .env.<environment>.local files.

    These loaded vars are only for local development and have no effect in production to the vars in a deployed Worker.
    Wrangler and Vite will continue to load .env files in order to configure themselves as a tool.

    Further details:

    • In vite build the local vars will be computed and stored in a .dev.vars file next to the compiled Worker code, so that vite preview can use them.
    • The wrangler types command will similarly read the .env files (if no .dev.vars files) in order to generate the Env interface.
    • If the CLOUDFLARE_LOAD_DEV_VARS_FROM_DOT_ENV environment variable is "false" then local dev variables will not be loaded from .env files.
    • If the CLOUDFLARE_INCLUDE_PROCESS_ENV environment variable is "true" then all the environment variables found on process.env will be included as local dev vars.
    • Wrangler (but not Vite plugin) also now supports the --env-file=<path/to/dotenv/file> global CLI option. This affects both loading .env to configure Wrangler the tool as well as loading local dev vars.
Patch Changes

v1.10.2

Compare Source

Patch Changes
microsoft/playwright (@​playwright/test)

v1.54.2

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/36714 - [Regression]: Codegen is not able to launch in Administrator Terminal on Windows (ProtocolError: Protocol error)https://github.com/microsoft/playwright/issues/368288 - [Regression]: Playwright Codegen keeps spamming with selected optiohttps://github.com/microsoft/playwright/issues/3681010 - [Regression]: Starting Codegen with target language doesn't work anymore

Browser Versions

  • Chromium 139.0.7258.5
  • Mozilla Firefox 140.0.2
  • WebKit 26.0

This version was also tested against the following stable channels:

  • Google Chrome 140
  • Microsoft Edge 140
rolldown/rolldown (@​rolldown/pluginutils)

v1.0.0-beta.30

Compare Source

💥 BREAKING CHANGES
🚀 Features
🐛 Bug Fixes
🚜 Refactor
📚 Documentation
⚡ Performance
🧪 Testing
⚙️ Miscellaneous Tasks
eslint-community/eslint-plugin-n (eslint-plugin-n)

v17.21.3

Compare Source

🩹 Fixes
ota-meshi/eslint-plugin-regexp (eslint-plugin-regexp)

v2.9.1

Compare Source

Patch Changes
  • fix(sort-character-class-elements): wrong autofix for ^ (#​859)
pnpm/pnpm (pnpm)

v10.14.0

Compare Source

Minor Changes

  • Added support for JavaScript runtime resolution

    Declare Node.js, Deno, or Bun in devEngines.runtime (inside package.json) and let pnpm download and pin it automatically.

    Usage example:

    {
  "devEngines": {
    "runtime": {
      "name": "node",
      "version": "^24.4.0",
      "onFail": "download" (we only support the "download" value for now)
    }
  }
}

    How it works:

    1. pnpm install resolves your specified range to the latest matching runtime version.
    2. The exact version (and checksum) is saved in the lockfile.
    3. Scripts use the local runtime, ensuring consistency across environments.

    Why this is better:

    1. This new setting supports also Deno and Bun (vs. our Node-only settings useNodeVersion and executionEnv.nodeVersion)
    2. Supports version ranges (not just a fixed version).
    3. The resolved version is stored in the pnpm lockfile, along with an integrity checksum for future validation of the Node.js content's validity.
    4. It can be used on any workspace project (like executionEnv.nodeVersion). So, different projects in a workspace can use different runtimes.
    5. For now devEngines.runtime setting will install the runtime locally, which we will improve in future versions of pnpm by using a shared location on the computer.

    Related PR: #​9755.

  • Add --cpu, --libc, and --os to pnpm install, pnpm add, and pnpm dlx to customize supportedArchitectures via the CLI #​7510.

Patch Changes
  • Fix a bug in which pnpm add downloads packages whose libc differ from pnpm.supportedArchitectures.libc.
  • The integrities of the downloaded Node.js artifacts are verified #​9750.
  • Allow dlx to parse CLI flags and options between the dlx command and the command to run or between the dlx command and -- #​9719.
  • pnpm install --prod should removing hoisted dev dependencies #​9782.
  • Fix an edge case bug causing local tarballs to not re-link into the virtual store. This bug would happen when changing the contents of the tarball without renaming the file and running a filtered install.
  • Fix a bug causing pnpm install to incorrectly assume the lockfile is up to date after changing a local tarball that has peers dependencies.
facebook/react (react)

v19.1.1

Compare Source

facebook/react (react-dom)

v19.1.1

Compare Source

facebook/react (react-is)

v19.1.1

Compare Source

React
toplenboren/simple-git-hooks (simple-git-hooks)

v2.13.1

Compare Source

Patch Changes
rolldown/tsdown (tsdown)

v0.13.2

Compare Source

   🚨 Upstream Breaking Changes
   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.13.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub
microsoft/TypeScript (typescript)

v5.9.2

Compare Source

vitejs/rolldown-vite (vite)

v7.0.12

Compare Source

Features
Bug Fixes
Miscellaneous Chores
  • update rolldown-plugin-dts (2c4159e)
cloudflare/workers-sdk (wrangler)

v4.27.0

Compare Source

Minor Changes

  • #​9914 a24c9d8 Thanks @​petebacondarwin! - Add support for loading local dev vars from .env files

    If there are no .dev.vars or .dev.vars.<environment> files, when running Wrangler or the Vite plugin in local development mode,
    they will now try to load additional local dev vars from .env, .env.local, .env.<environment> and .env.<environment>.local files.

    These loaded vars are only for local development and have no effect in production to the vars in a deployed Worker.
    Wrangler and Vite will continue to load .env files in order to configure themselves as a tool.

    Further details:

    • In vite build the local vars will be computed and stored in a .dev.vars file next to the compiled Worker code, so that vite preview can use them.
    • The wrangler types command will similarly read the .env files (if no .dev.vars files) in order to generate the Env interface.
    • If the CLOUDFLARE_LOAD_DEV_VARS_FROM_DOT_ENV environment variable is "false" then local dev variables will not be loaded from .env files.
    • If the CLOUDFLARE_INCLUDE_PROCESS_ENV environment variable is "true" then all the environment variables found on process.env will be included as local dev vars.
    • Wrangler (but not Vite plugin) also now supports the --env-file=<path/to/dotenv/file> global CLI option. This affects both loading .env to configure Wrangler the tool as well as loading local dev vars.
Patch Changes

  • #​10051 0f7820e Thanks @​nikitassharma! - Add support for custom instance limits for containers. For example, instead of
    having to use the preconfigured dev/standard/basic instance types, you can now
    set:

    instance_type: {
  vcpu: 1,
  memory_mib: 1024,
  disk_mb: 4000
}

    This feature is currently only available to customers on an enterprise plan.

  • #​10149 e9bb8d3 Thanks @​vicb! - fix require("debug") in nodejs_compat mode

  • Updated dependencies [9b61f44]:

v4.26.1

Compare Source

Patch Changes

  • #​10061 f8a80a8 Thanks @​emily-shen! - feat(containers): try to automatically get the socket path that the container engine is listening on.

    Currently, if your container engine isn't set up to listen on unix:///var/run/docker.sock (or isn't symlinked to that), then you have to manually set this via the dev.containerEngine field in your Wrangler config, or via the env vars WRANGLER_DOCKER_HOST. This change means that we will try and get the socket of the current context automatically. This should reduce the occurrence of opaque internal errors thrown by the runtime when the daemon is not listening on unix:///var/run/docker.sock.

    In addition to WRANGLER_DOCKER_HOST, DOCKER_HOST can now also be used to set the container engine socket address.

  • #​10048 dbdbb8c Thanks @​vicb! - pass the compatibility date and flags to the unenv preset

  • #​10096 687655f Thanks @​vicb! - bump unenv to 2.0.0-rc.19

  • #​9897 755a249 Thanks @​edmundhung! - fix: wrangler types should infer the types of the default worker entrypoint

  • Updated dependencies [82a5b2e, f8f7352, 2df1d06, dbdbb8c, 5991a9c, 687655f]:

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 added the dependencies label Aug 4, 2025
@hi-ogawa hi-ogawa merged commit 61d777d into main Aug 4, 2025
28 of 29 checks passed
@hi-ogawa hi-ogawa deleted the renovate/all-minor-patch branch August 4, 2025 05:08
This was referenced Aug 4, 2025
Closed
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@hi-ogawa