Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Sep 29, 2025

Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.

This PR contains the following updates:

Package Change Age Confidence
@cloudflare/vite-plugin (source) ^1.13.3 -> ^1.13.7 age confidence
@playwright/test (source) ^1.55.0 -> ^1.55.1 age confidence
@rolldown/pluginutils (source) 1.0.0-beta.38 -> 1.0.0-beta.41 age confidence
@tailwindcss/typography ^0.5.18 -> ^0.5.19 age confidence
@tsconfig/strictest (source) ^2.0.5 -> ^2.0.6 age confidence
@types/node (source) ^22.18.6 -> ^22.18.7 age confidence
@types/react (source) ^19.1.13 -> ^19.1.16 age confidence
lint-staged ^16.1.6 -> ^16.2.3 age confidence
playwright-chromium (source) ^1.55.0 -> ^1.55.1 age confidence
pnpm (source) 10.17.0 -> 10.17.1 age confidence
react-router (source) 7.9.1 -> 7.9.3 age confidence
rolldown (source) 1.0.0-beta.38 -> 1.0.0-beta.41 age confidence
tsdown ^0.15.4 -> ^0.15.5 age confidence
typescript-eslint (source) ^8.44.0 -> ^8.45.0 age confidence
vite (source) ^7.1.13 -> ^7.1.14 age confidence
vite (source) ^7.1.6 -> ^7.1.7 age confidence
wrangler (source) ^4.38.0 -> ^4.40.2 age confidence

Release Notes

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

v1.13.7

Compare Source

Patch Changes
  • Updated dependencies [b455281]:
    • wrangler@​4.40.2

v1.13.6

Compare Source

Patch Changes
  • Updated dependencies [a57149f]:
    • wrangler@​4.40.1

v1.13.5

Compare Source

Patch Changes

v1.13.4

Compare Source

Patch Changes
  • #​10677 d7aa0ae Thanks @​edmundhung! - Support Hyperdrive local connection strings from .env files

    You can now define your Hyperdrive local connection string in a .env file using the CLOUDFLARE_HYPERDRIVE_LOCAL_CONNECTION_STRING_<BINDING_NAME> variable.

    CLOUDFLARE_HYPERDRIVE_LOCAL_CONNECTION_STRING_PROD_DB="postgres://user:password@127.0.0.1:5432/testdb"
  • Updated dependencies [555a6da, 262393a, 3ec1f65, a434352, 328e687, 97a72cc, b4a4311, dc1d0d6, acd48ed, 55a10a3]:

    • miniflare@​4.20250923.0
    • wrangler@​4.39.0
microsoft/playwright (@​playwright/test)

v1.55.1

Compare Source

Highlights

#​37479 - [Bug]: Upgrade Chromium to 140.0.7339.186.
#​37147 - [Regression]: Internal error: step id not found.
#​37146 - [Regression]: HTML reporter displays a broken chip link when there are no projects.
#​37137 - Revert "fix(a11y): track inert elements as hidden".

Browser Versions

  • Chromium 140.0.7339.186
  • Mozilla Firefox 141.0
  • WebKit 26.0

This version was also tested against the following stable channels:

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

v1.0.0-beta.41

Compare Source

🚀 Features
🐛 Bug Fixes
  • 'asset' module type and CJS format produces warnings and wrong output (#​6369) by @​IWANABETHATGUY
  • inlining constants in CJS by optimization.inlineConst incorrectly inlines non-constant values if the value is assigned more than once (#​6328) by @​IWANABETHATGUY
  • dev: add hasLatestBuildOutput instead of scheduleBuildIfStale and add edit-reload test (#​6321) by @​sapphi-red
🚜 Refactor
⚡ Performance
🧪 Testing
⚙️ Miscellaneous Tasks

v1.0.0-beta.40

Compare Source

🚀 Features
🐛 Bug Fixes
  • rolldown_plugin_react_refresh_wrapper: avoid using cwd to allow using as a callable plugin (#​6318) by @​sapphi-red
  • rolldown_plugin_transform: resolve tsconfig from absolute path (#​6311) by @​shulaoda
🚜 Refactor
📚 Documentation
⚡ Performance
⚙️ Miscellaneous Tasks

v1.0.0-beta.39

Compare Source

🚀 Features
🐛 Bug Fixes
🚜 Refactor
📚 Documentation
⚡ Performance
🧪 Testing
⚙️ Miscellaneous Tasks
❤️ New Contributors
tailwindlabs/tailwindcss-typography (@​tailwindcss/typography)

v0.5.19

Compare Source

Fixed
  • Fixed broken color styles (#​405)
tsconfig/bases (@​tsconfig/strictest)

v2.0.6

Compare Source

lint-staged/lint-staged (lint-staged)

v16.2.3

Compare Source

Patch Changes
  • #​1669 27cd541 Thanks @​iiroj! - When using --fail-on-changes, automatically hidden (partially) unstaged changes are no longer counted to make lint-staged fail.

v16.2.2

Compare Source

Patch Changes
  • #​1667 699f95d Thanks @​iiroj! - The backup stash will not be dropped when using --fail-on-changes and there are errors. When reverting to original state is disabled (via --no-revert or --fail-on-changes), hidden (partially) unstaged changes are still restored automatically so that it's easier to resolve the situation manually.

    Additionally, the example for using the backup stash manually now uses the correct backup hash, if available:

    % npx lint-staged --fail-on-changes
    ✔ Backed up original state in git stash (c18d55a3)
    ✔ Running tasks for staged files...
    ✖ Tasks modified files and --fail-on-changes was used!
    ↓ Cleaning up temporary files...
    
    ✖ lint-staged failed because `--fail-on-changes` was used.
    
    Any lost modifications can be restored from a git stash:
    
      > git stash list --format="%h %s"
      c18d55a3 On main: lint-staged automatic backup
      > git apply --index c18d55a3

v16.2.1

Compare Source

Patch Changes
  • #​1664 8277b3b Thanks @​iiroj! - The built-in TypeScript types have been updated to more closely match the implementation. Notably, the list of staged files supplied to task functions is readonly string[] and can't be mutated. Thanks @​outslept!

    export default {
    ---  "*": (files: string[]) => void console.log('staged files', files)
    +++  "*": (files: readonly string[]) => void console.log('staged files', files)
    }
  • #​1654 70b9af3 Thanks @​iiroj! - This version has been published from GitHub Actions using Trusted Publishing for npm packages.

  • #​1659 4996817 Thanks @​iiroj! - Fix searching configuration files when the working directory is a subdirectory of a git repository, and there are package.json files in the working directory. This situation might happen when running lint-staged for a single package in a monorepo.

  • #​1654 7021f0a Thanks @​iiroj! - Return the caret semver range (^) to direct dependencies so that future patch and minor versions are allowed. This enables projects to better maintain and deduplicate their own transitive dependencies while not requiring direct updates to lint-staged. This was changed in 16.2.0 after the vulnerability issues with chalk and debug, which were also removed in the same version.

    Given the recent vulnerabilities in the npm ecosystem, it's best to be very careful when updating dependencies.

v16.2.0

Compare Source

Minor Changes
  • #​1615 99eb742 Thanks @​iiroj! - Added a new option --fail-on-changes to make lint-staged exit with code 1 when tasks modify any files, making the precommit hook fail. This is similar to the git diff --exit-code option. Using this flag also implies the --no-revert flag which means any changes made my tasks will be left in the working tree after failing, so that they can be manually staged and the commit tried again.

  • #​1611 cd05fd3 Thanks @​rlorenzo! - Added a new option --continue-on-error so that lint-staged will run all tasks to completion even if some of them fail. By default, lint-staded will exit early on the first failure.

  • #​1637 82fcc07 Thanks @​iiroj! - Internal lint-staged errors are now thrown and visible in the console output. Previously they were caught with the process exit code set to 1, but not logged. This happens when, for example, there's a syntax error in the lint-staged configuration file.

  • #​1647 a5ecc06 Thanks @​iiroj! - Remove debug as a dependency due to recent malware issue; read more at debug-js/debug#1005. Because of this, the DEBUG environment variable is no longer supported — use the --debug to enable debugging

  • #​1636 8db2717 Thanks @​iiroj! - Added a new option --hide-unstaged so that lint-staged will hide all unstaged changes to tracked files before running tasks. The changes will be applied back after running the tasks. Note that the combination of flags --hide-unstaged --no-hide-partially-staged isn't meaningful and behaves the same as just --hide-unstaged.

    Thanks to @​ItsNickBarry for the idea and initial implementation in #​1552.

  • #​1648 7900b3b Thanks @​iiroj! - Remove lilconfig to reduce reliance on third-party dependencies. It was used to find possible config files outside of those tracked in Git, including from the parent directories. This behavior has been moved directly into lint-staged and should work about the same.

Patch Changes
pnpm/pnpm (pnpm)

v10.17.1

Compare Source

Patch Changes
  • When a version specifier cannot be resolved because the versions don't satisfy the minimumReleaseAge setting, print this information out in the error message #​9974.
  • Fix state.json creation path when executing pnpm patch in a workspace project #​9733.
  • When minimumReleaseAge is set and the latest tag is not mature enough, prefer a non-deprecated version as the new latest #​9987.
remix-run/react-router (react-router)

v7.9.3

Compare Source

Patch Changes
  • Do not try to use turbo-stream to decode CDN errors that never reached the server (#​14385)

    • We used to do this but lost this check with the adoption of single fetch
  • Fix Data Mode regression causing a 404 during initial load in when middleware exists without any loader functions (#​14393)

v7.9.2

Compare Source

Patch Changes
    • Update client-side router to run client middleware on initial load even if no loaders exist (#​14348)
    • Update createRoutesStub to run route middleware
      • You will need to set the <RoutesStub future={{ v8_middleware: true }} /> flag to enable the proper context type
  • Update Lazy Route Discovery manifest requests to use a singular comma-separated paths query param instead of repeated p query params (#​14321)

    • This is because Cloudflare has a hard limit of 100 URL search param key/value pairs when used as a key for caching purposes
    • If more that 100 paths were included, the cache key would be incomplete and could produce false-positive cache hits
  • [UNSTABLE] Add fetcher.unstable_reset() API (#​14206)

  • Made useOutlet element reference have stable identity in-between route chages (#​13382)

  • feat: enable full transition support for the rsc router (#​14362)

  • In RSC Data Mode, handle SSR'd client errors and re-try in the browser (#​14342)

  • Support middleware prop on <Route> for usage with a data router via createRoutesFromElements (#​14357)

  • Handle encoded question mark and hash characters in ancestor splat routes (#​14249)

  • Fail gracefully on manifest version mismatch logic if sessionStorage access is blocked (#​14335)

rolldown/tsdown (tsdown)

v0.15.5

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub
typescript-eslint/typescript-eslint (typescript-eslint)

v8.45.0

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

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

v8.44.1

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

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

vitejs/rolldown-vite (vite)

v7.1.14

Compare Source

Features
Bug Fixes
  • use readFileSync to avoid "too many open files" (7c7ffdc)
Performance Improvements
  • use single regex for isEntirelyImport (ac1ceaf)
Documentation
Miscellaneous Chores
cloudflare/workers-sdk (wrangler)

v4.40.2

Compare Source

Patch Changes

v4.40.1

Compare Source

Patch Changes

v4.40.0

Compare Source

Minor Changes
  • #​10743 a7ac751 Thanks @​jonesphillip! - Changes --fileSizeMB to --file-size for wrangler r2 bucket catalog compaction command.
    Small fixes for pipelines commands.
Patch Changes
  • #​10706 81fd733 Thanks @​1000hz! - Fixed an issue that caused some Workers to have an incorrect service tag applied when using a redirected configurat

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
Copy link
Contributor Author

renovate bot commented Sep 29, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact 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: pnpm-lock.yaml
Scope: all 44 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
.../playground/base-path                 |  WARN  Installing a dependency from a non-existent directory: /tmp/renovate/repos/github/vitejs/vite-plugin-react/packages/plugin-react-swc/dist
.../playground/class-components          |  WARN  Installing a dependency from a non-existent directory: /tmp/renovate/repos/github/vitejs/vite-plugin-react/packages/plugin-react-swc/dist
.../playground/decorators                |  WARN  Installing a dependency from a non-existent directory: /tmp/renovate/repos/github/vitejs/vite-plugin-react/packages/plugin-react-swc/dist
.../plugin-react-swc/playground/emotion  |  WARN  Installing a dependency from a non-existent directory: /tmp/renovate/repos/github/vitejs/vite-plugin-react/packages/plugin-react-swc/dist
.../playground/emotion-plugin            |  WARN  Installing a dependency from a non-existent directory: /tmp/renovate/repos/github/vitejs/vite-plugin-react/packages/plugin-react-swc/dist
packages/plugin-react-swc/playground/hmr |  WARN  Installing a dependency from a non-existent directory: /tmp/renovate/repos/github/vitejs/vite-plugin-react/packages/plugin-react-swc/dist
packages/plugin-react-swc/playground/mdx |  WARN  Installing a dependency from a non-existent directory: /tmp/renovate/repos/github/vitejs/vite-plugin-react/packages/plugin-react-swc/dist
.../plugin-react-swc/playground/react-18 |  WARN  Installing a dependency from a non-existent directory: /tmp/renovate/repos/github/vitejs/vite-plugin-react/packages/plugin-react-swc/dist
.../playground/shadow-export             |  WARN  Installing a dependency from a non-existent directory: /tmp/renovate/repos/github/vitejs/vite-plugin-react/packages/plugin-react-swc/dist
Progress: resolved 23, reused 0, downloaded 0, added 0
.../playground/styled-components         |  WARN  Installing a dependency from a non-existent directory: /tmp/renovate/repos/github/vitejs/vite-plugin-react/packages/plugin-react-swc/dist
.../plugin-react-swc/playground/ts-lib   |  WARN  Installing a dependency from a non-existent directory: /tmp/renovate/repos/github/vitejs/vite-plugin-react/packages/plugin-react-swc/dist
.../plugin-react-swc/playground/worker   |  WARN  Installing a dependency from a non-existent directory: /tmp/renovate/repos/github/vitejs/vite-plugin-react/packages/plugin-react-swc/dist
Progress: resolved 55, reused 0, downloaded 0, added 0
Progress: resolved 82, reused 0, downloaded 0, added 0
Progress: resolved 85, reused 0, downloaded 0, added 0
/tmp/renovate/repos/github/vitejs/vite-plugin-react/packages/plugin-react:
 ERR_PNPM_NO_MATCHING_VERSION  No matching version found for vite@7.1.13 while fetching it from https://registry.npmjs.org/

This error happened while installing the dependencies of vitest@3.2.4

The latest release of vite is "7.1.7".

Other releases are:
  * alpha: 6.0.0-alpha.24
  * beta: 7.1.0-beta.1
  * previous: 5.4.20

If you need the full list of all 675 published versions run "$ pnpm view vite versions".

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from bc83180 to e24cf39 Compare September 30, 2025 02:16
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from e24cf39 to 17f5c39 Compare September 30, 2025 07:37
@hi-ogawa hi-ogawa merged commit 407795d into main Sep 30, 2025
20 checks passed
@hi-ogawa hi-ogawa deleted the renovate/all-minor-patch branch September 30, 2025 08:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants