Skip to content

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

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
hi-ogawa merged 2 commits into from
Dec 8, 2025
Merged

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

hi-ogawa merged 2 commits into from
Dec 8, 2025

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Dec 8, 2025 •
edited
Loading

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@cloudflare/vite-plugin (source) ^1.15.3 -> ^1.17.0 age confidence
@rolldown/pluginutils (source) 1.0.0-beta.52 -> 1.0.0-beta.53 age confidence
react-router (source) 7.9.6 -> 7.10.1 age confidence
rolldown (source) 1.0.0-beta.52 -> 1.0.0-beta.53 age confidence
tsdown (source) ^0.16.8 -> ^0.17.1 age confidence
typescript-eslint (source) ^8.48.0 -> ^8.48.1 age confidence
vite (source) ^7.2.8 -> ^7.2.10 age confidence
vite (source) ^7.2.4 -> ^7.2.7 age confidence
vitest (source) ^4.0.14 -> ^4.0.15 age confidence
wrangler (source) ^4.51.0 -> ^4.53.0 age confidence

Release Notes

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

v1.17.0

Compare Source

Minor Changes
Patch Changes

v1.16.1

Compare Source

Patch Changes
  • Updated dependencies [59534ba, 7e80340]:
    • miniflare@​4.20251202.0
    • wrangler@​4.52.1

v1.16.0

Compare Source

Minor Changes

  • #​11445 c8e22c3 Thanks @​ascorbic! - Allow Worker config to be customized in the plugin config

    The Vite plugin can now be used to generate a Worker configuration instead of needing a Wrangler config file, or to customize an existing user-provided configuration.

    This is done via a new config option on the plugin, which accepts either a partial Worker configuration object, or a function that receives the current configuration and returns a partial config object, or modifies the current config in place.

    import cloudflare from "@​cloudflare/vite-plugin";
import { defineConfig } from "vite";

// Define a partial config object

export default defineConfig({
	plugins: [
		cloudflare({
			config: {
				compatibility_date: "2025-01-01",
			},
		}),
	],
});

// Return a partial config from a function, conditional on some logic

export default defineConfig({
	plugins: [
		cloudflare({
			config: (workerConfig) => {
				if (workerConfig.name === "my-worker") {
					return {
						compatibility_flags: ["nodejs_compat"],
					};
				}
			},
		}),
	],
});

// Modify the config in place

export default defineConfig({
	plugins: [
		cloudflare({
			config: (workerConfig) => {
				workerConfig.compatibility_date = "2025-01-01";
			},
		}),
	],
});

  • #​11360 6b38532 Thanks @​emily-shen! - Containers: Allow users to directly authenticate external image registries in local dev

    Previously, we always queried the API for stored registry credentials and used those to pull images. This means that if you are using an external registry (ECR, dockerhub) then you have to configure registry credentials remotely before running local dev.

    Now you can directly authenticate with your external registry provider (using docker login etc.), and Wrangler or Vite will be able to pull the image specified in the containers.image field in your config file.

    The Cloudflare-managed registry (registry.cloudflare.com) currently still does not work with the Vite plugin.

  • #​11408 f29e699 Thanks @​ascorbic! - Support zero-config operation

    If the Vite plugin is used in a project without an existing Wrangler config file, it should be able to operate in "zero-config" mode by generating a default Wrangler configuration for an assets-only worker.

  • #​11417 2ca70b1 Thanks @​jamesopstad! - Register named entrypoints with the dev registry.

    This enables binding to named entrypoints defined in a vite dev session from another vite dev or wrangler dev session running locally.

Patch Changes
rolldown/rolldown (@​rolldown/pluginutils)

v1.0.0-beta.53

Compare Source

💥 BREAKING CHANGES
🚀 Features
🐛 Bug Fixes
🚜 Refactor
📚 Documentation
⚡ Performance
  • rolldown_plugin_vite_css_post: lazily load cssScopeTo from JS module options (#​7253) by @​shulaoda
  • rolldown_plugin_vite_css_post: avoid unnecessary string clones in resolve_asset_urls_in_css (#​7250) by @​shulaoda
🧪 Testing
⚙️ Miscellaneous Tasks
❤️ New Contributors
remix-run/react-router (react-router)

v7.10.1

Compare Source

Patch Changes
  • Update the useOptimistic stub we provide for React 18 users to use a stable setter function to avoid potential useEffect loops - specifically when using <Link viewTransition> (#​14628)

v7.10.0

Compare Source

Minor Changes

  • Stabilize fetcher.reset() (#​14545)

    • ⚠️ This is a breaking change if you have begun using fetcher.unstable_reset()

  • Stabilize the dataStrategy match.shouldRevalidateArgs/match.shouldCallHandler() APIs. (#​14592)

    • The match.shouldLoad API is now marked deprecated in favor of these more powerful alternatives

    • If you're using this API in a custom dataStrategy today, you can swap to the new API at your convenience:

      // Before
const matchesToLoad = matches.filter((m) => m.shouldLoad);

// After
const matchesToLoad = matches.filter((m) => m.shouldCallHandler());

    • match.shouldRevalidateArgs is the argument that will be passed to the route shouldRevaliate function

    • Combined with the parameter accepted by match.shouldCallHandler, you can define a custom revalidation behavior for your dataStrategy:

    const matchesToLoad = matches.filter((m) => {
  const defaultShouldRevalidate = customRevalidationBehavior(
    match.shouldRevalidateArgs,
  );
  return m.shouldCallHandler(defaultShouldRevalidate);
  // The argument here will override the internal `defaultShouldRevalidate` value
});
Patch Changes

  • Fix a Framework Mode bug where the defaultShouldRevalidate parameter to shouldRevalidate would not be correct after action returned a 4xx/5xx response (true when it should have been false) (#​14592)

    • If your shouldRevalidate function relied on that parameter, you may have seen unintended revalidations

  • Fix fetcher.submit failing with plain objects containing a tagName property (#​14534)

  • [UNSTABLE] Add unstable_pattern to the parameters for client side unstable_onError, refactor how it's called by RouterProvider to avoid potential strict mode issues (#​14573)

  • Add new unstable_useTransitions flag to routers to give users control over the usage of React.startTransition and React.useOptimistic. (#​14524)

    • Framework Mode + Data Mode:
      • <HydratedRouter unstable_transition>/<RouterProvider unstable_transition>
      • When left unset (current default behavior)
        • Router state updates are wrapped in React.startTransition
        • ⚠️ This can lead to buggy behaviors if you are wrapping your own navigations/fetchers in React.startTransition
        • You should set the flag to true if you run into this scenario to get the enhanced useOptimistic behavior (requires React 19)
      • When set to true
        • Router state updates remain wrapped in React.startTransition (as they are without the flag)
        • Link/Form navigations will be wrapped in React.startTransition
        • A subset of router state info will be surfaced to the UI during navigations via React.useOptimistic (i.e., useNavigation(), useFetchers(), etc.)
          • ⚠️ This is a React 19 API so you must also be React 19 to opt into this flag for Framework/Data Mode
      • When set to false
        • The router will not leverage React.startTransition or React.useOptimistic on any navigations or state changes
    • Declarative Mode
      • <BrowserRouter unstable_useTransitions>
      • When left unset
        • Router state updates are wrapped in React.startTransition
      • When set to true
        • Router state updates remain wrapped in React.startTransition (as they are without the flag)
        • Link/Form navigations will be wrapped in React.startTransition
      • When set to false
        • the router will not leverage React.startTransition on any navigations or state changes

  • Fix the promise returned from useNavigate in Framework/Data Mode so that it properly tracks the duration of popstate navigations (i.e., navigate(-1)) (#​14524)

  • Fix internal type error in useRoute types that surfaces when skipLibCheck is disabled (#​14577)

  • Preserve statusText on the ErrorResponse instance when throwing data() from a route handler (#​14555)

  • Optimize href() to avoid backtracking regex on splat (#​14329)

rolldown/tsdown (tsdown)

v0.17.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.17.0

Compare Source

   🚨 Breaking Changes

Notable features: https://bsky.app/profile/sxzz.dev/post/3m6xi7e7d5k2b

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

v8.48.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.2.10

Compare Source

Features
Bug Fixes
Documentation
Tests

v7.2.9

Compare Source

Bug Fixes
Miscellaneous Chores
vitejs/vite (vite)

v7.2.7

Compare Source

v7.2.6

Compare Source

7.2.6 (2025-12-01)

vitest-dev/vitest (vitest)

v4.0.15

Compare Source

   🚀 Experimental Features
   🐞 Bug Fixes
    View changes on GitHub
cloudflare/workers-sdk (wrangler)

v4.53.0

Compare Source

Minor Changes

  • #​11500 af54c63 Thanks @​dario-piotrowicz! - Add new autoconfig_summary field to the deploy output entry

    This change augments wrangler deploy output being printed to WRANGLER_OUTPUT_FILE_DIRECTORY or WRANGLER_OUTPUT_FILE_PATH to also include a new autoconfig_summary field containing the possible summary details for the autoconfig process (the field is undefined if autoconfig didn't run).

    Note: the field is experimental and could change while autoconfig is not GA

  • #​11477 9988cc9 Thanks @​ascorbic! - Support Nuxt in autoconfig

  • #​11472 ce295bf Thanks @​dario-piotrowicz! - Support Qwik projects in autoconfig

  • #​10937 9514c9a Thanks @​ReppCodes! - Add support for "targeted" placement mode with region, host, and hostname fields

    This change adds a new mode to placement configuration. You can specify one of the following fields to target specific external resources for Worker placement:

    • region: Specify a region identifier (e.g., "aws:us-east-1") to target a region from another cloud service provider
    • host: Specify a host with (required) port (e.g., "example.com:8123") to target a TCP service
    • hostname: Specify a hostname (e.g., "example.com") to target an HTTP resource

    These fields are mutually exclusive - only one can be specified at a time.

    Example configuration:

    [placement]
host = "example.com:8123"

  • #​11498 ac861f8 Thanks @​penalosa! - Add React Router support in autoconfig

  • #​11506 79d30d4 Thanks @​vicb! - Set the target JS version to ES2024

Patch Changes

v4.52.1

Compare Source

Patch Changes

v4.52.0

Compare Source

Minor Changes

  • #​11416 abe49d8 Thanks @​dario-piotrowicz! - Remove the wrangler deploy's --x-remote-diff-check experimental flag

    The remote diffing feature has been enabled by default for a while and its functionality is stable, as a result the experimental flag (only available for option-out of the feature right now) has been removed.

  • #​11408 f29e699 Thanks @​ascorbic! - Export unstable helpers useful for generating wrangler config

  • #​11389 2342d2f Thanks @​dario-piotrowicz! - Improve the wrangler deploy flow to also check for potential overrides of secrets.

    Now when you run wrangler deploy Wrangler will check the remote secrets for your workers for conflicts with the names of the bindings you're about to deploy. If there are conflicts, Wrangler will warn you and ask you for your permission before proceeding.

  • #​11375 9a1de61 Thanks @​penalosa! - Support TanStack Start in autoconfig

  • #​11360 6b38532 Thanks @​emily-shen! - Containers: Allow users to directly authenticate external image registries in local dev

    Previously, we always queried the API for stored registry credentials and used those to pull images. This means that if you are using an external registry (ECR, dockerhub) then you have to configure registry credentials remotely before running local dev.

    Now you can directly authenticate with your external registry provider (using docker login etc.), and Wrangler or Vite will be able to pull the image specified in the containers.image field in your

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 Dec 8, 2025
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from aad6d7d to 86c3751 Compare December 8, 2025 05:50
@renovate
Copy link
Contributor Author

renovate bot commented Dec 8, 2025

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@hi-ogawa hi-ogawa merged commit 1f372b6 into main Dec 8, 2025
20 checks passed
@hi-ogawa hi-ogawa deleted the renovate/all-minor-patch branch December 8, 2025 08:34
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.

2 participants

@hi-ogawa