Skip to content

Update Routine updates#40

Merged
renovate[bot] merged 1 commit intomainfrom
renovate/routine-updates
Feb 9, 2026
Merged

Update Routine updates#40
renovate[bot] merged 1 commit intomainfrom
renovate/routine-updates

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 9, 2026

This PR contains the following updates:

Package Change Age Confidence
@types/node (source) 20.19.3020.19.32 age confidence
@types/react (source) 19.2.1019.2.13 age confidence
@vitejs/plugin-react (source) 5.1.25.1.3 age confidence
autoprefixer 10.4.2310.4.24 age confidence
eslint-plugin-react-refresh 0.4.260.5.0 age confidence
pkg-pr-new (source) 0.0.620.0.63 age confidence
remeda (source) 2.33.42.33.5 age confidence
wrangler (source) 4.61.14.63.0 age confidence

Release Notes

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

v5.1.3

Compare Source

postcss/autoprefixer (autoprefixer)

v10.4.24

Compare Source

  • Made Autoprefixer a little faster (by @​Cherry).
ArnaudBarre/eslint-plugin-react-refresh (eslint-plugin-react-refresh)

v0.5.0

Compare Source

Breaking changes
  • The package now ships as ESM and requires ESLint 9 + node 20. Because legacy config doesn't support ESM, this requires to use flat config
  • A new reactRefresh export is available and prefered over the default export. It's an object with two properties:
    • plugin: The plugin object with the rules
    • configs: An object containing configuration presets, each exposed as a function. These functions accept your custom options, merge them with sensible defaults for that config, and return the final config object.
  • customHOCs option was renamed to extraHOCs
  • Validation of HOCs calls is now more strict, you may need to add some HOCs to the extraHOCs option

Config example:

import { defineConfig } from "eslint/config";
import { reactRefresh } from "eslint-plugin-react-refresh";

export default defineConfig(
  /* Main config */
  reactRefresh.configs.vite({ extraHOCs: ["someLibHOC"] }),
);

Config example without config:

import { defineConfig } from "eslint/config";
import { reactRefresh } from "eslint-plugin-react-refresh";

export default defineConfig({
  files: ["**/*.ts", "**/*.tsx"],
  plugins: {
    // other plugins
    "react-refresh": reactRefresh.plugin,
  },
  rules: {
    // other rules
    "react-refresh/only-export-components": [
      "warn",
      { extraHOCs: ["someLibHOC"] },
    ],
  },
});
Why

This version follows a revamp of the internal logic to better make the difference between random call expressions like export const Enum = Object.keys(Record) and actual React HOC calls like export const MemoComponent = memo(Component). (fixes #​93)

The rule now handles ternaries and patterns like export default customHOC(props)(Component) which makes it able to correctly support files like this one given this config:

{
  "react-refresh/only-export-components": [
    "warn",
    { "extraHOCs": ["createRootRouteWithContext"] }
  ]
}

[!NOTE]
Actually createRoute functions from TanStack Router are not React HOCs, they return route objects that fake to be a memoized component but are not. When only doing createRootRoute({ component: Foo }), HMR will work fine, but as soon as you add a prop to the options that is not a React component, HMR will not work. I would recommend to avoid adding any TanStack function to extraHOCs it you want to preserve good HMR in the long term. Bluesky thread.

Because I'm not 100% sure this new logic doesn't introduce any false positive, this is done in a major-like version. This also give me the occasion to remove the hardcoded connect from the rule. If you are using connect from react-redux, you should now add it to extraHOCs like this:

{
  "react-refresh/only-export-components": ["warn", { "extraHOCs": ["connect"] }]
}
stackblitz-labs/pkg.pr.new (pkg-pr-new)

v0.0.63

Compare Source

remeda/remeda (remeda)

v2.33.5

Compare Source

Bug Fixes
cloudflare/workers-sdk (wrangler)

v4.63.0

Compare Source

Minor Changes
  • #​12386 447daa3 Thanks @​NuroDev! - Added new "open local explorer" hotkey for experimental/WIP local resource explorer

    When running wrangler dev with the experimental local explorer feature enabled, you can now press the e hotkey to open the local resource explorer UI in your browser.

Patch Changes
  • #​11350 ee9b81f Thanks @​dario-piotrowicz! - fix: improve error message when the entrypoint is incorrect

    Error messages for incorrect entrypoint configuration have been improved to provide clearer and more actionable feedback. The updated messages help users understand what went wrong and how to fix their configuration.

  • #​12402 63f1adb Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20260131.0 1.20260203.0
  • #​12418 ba13de9 Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20260203.0 1.20260205.0
  • #​12216 fe3af35 Thanks @​ichernetsky-cf! - Deprecate 'wrangler cloudchamber apply' in favor of 'wrangler deploy'

  • #​12368 bd4bb98 Thanks @​KianNH! - Preserve Containers configuration when using versions commands

    Previously, commands like wrangler versions upload would inadvertently disable Containers on associated Durable Object namespaces because the containers property was being omitted from the API request body.

  • #​12396 dab4bc9 Thanks @​petebacondarwin! - fix: redact email addresses and account names in non-interactive mode

    To prevent sensitive information from being exposed in public CI logs, email addresses and account names are now redacted when running in non-interactive mode (e.g., CI environments). Account IDs remain visible to aid debugging.

  • #​12378 18c0784 Thanks @​X6TXY! - Truncate Pages commit messages at UTF-8 boundaries to avoid invalid UTF-8

  • Updated dependencies [63f1adb, ba13de9, 83adb2c]:

    • miniflare@​4.20260205.0

v4.62.0

Compare Source

Minor Changes
  • #​12064 964a39d Thanks @​G4brym! - Add AI Search OAuth scopes to login

    Adds ai-search:write and ai-search:run OAuth scopes to the default login scopes, enabling wrangler to authenticate with AI Search APIs.

  • #​11867 253a85d Thanks @​rahulsuresh-git! - Add wrangler r2 bucket local-uploads command to manage local uploads for R2 buckets

    When enabled, object data is written to the nearest region first, then asynchronously replicated to the bucket's primary region.

    Docs: https://developers.cloudflare.com/r2/buckets/local-uploads

    # Get local uploads status
    wrangler r2 bucket local-uploads get my-bucket
    
    # Enable local uploads (will prompt for confirmation)
    wrangler r2 bucket local-uploads enable my-bucket
    
    # Enable without confirmation prompt
    wrangler r2 bucket local-uploads enable my-bucket --force
    
    # Disable local uploads
    wrangler r2 bucket local-uploads disable my-bucket
  • #​11803 1bd1488 Thanks @​dario-piotrowicz! - Add a new subrequests limit to the limits field of the Wrangler configuration file

    Before only the cpu_ms limit was supported in the limits field of the Wrangler configuration file, now a subrequests limit can be specified as well which enables the user to limit the number of fetch requests that a Worker's invocation can make.

    Example:

    {
    	"$schema": "./node_modules/wrangler/config-schema.json",
    	"limits": {
    		"cpu_ms": 1000,
    		"subrequests": 150 // newly added field
    	}
    }
  • #​12185 f7aa8c7 Thanks @​penalosa! - Add timestamp field to the version metadata binding in local development. The version metadata binding now includes id, tag, and timestamp fields, making it easier to test version-aware logic locally.

Patch Changes
  • #​12190 ce736b9 Thanks @​dario-piotrowicz! - Update autoconfig logic to handle Next.js projects by using the new @opennextjs/cloudflare migrate command

  • #​12065 47944d1 Thanks @​langningchen! - Improve error message when d1 export --output points to a directory

  • #​12292 4c4d5a5 Thanks @​dario-piotrowicz! - Add versionCommand to the autoconfig_summary field in the autoconfig output entry

    Add the version upload command to the output being printed by wrangler deploy to WRANGLER_OUTPUT_FILE_DIRECTORY/WRANGLER_OUTPUT_FILE_PATH. This complements the existing buildCommand and deployCommand fields and allows CI systems to know how to upload new versions of Workers.

    For example, for a standard npm project this would be:

    • Version command: npx wrangler versions upload

    While for a Next.js project it would be:

    • Version command: npx @​opennextjs/cloudflare upload
  • #​12050 b05b919 Thanks @​NuroDev! - Fixed Wrangler's error handling for both invalid commands with and without the --help flag, ensuring consistent and clear error messages.

    Additionally, it also ensures that if you provide an invalid argument to a valid command, Wrangler will now correctly display that specific commands help menu.

  • #​12289 0aaf080 Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20260128.0 1.20260129.0
  • #​12295 b981db5 Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20260129.0 1.20260130.0
  • #​12355 a113c0d Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20260130.0 1.20260131.0
  • #​11971 fdd7a9f Thanks @​dario-piotrowicz! - Add framework id, build command, and deploy command to the autoconfig_summary field in the deploy output entry

    Add the framework id alongside the commands to build and deploy the project to the output being printed by wrangler deploy to WRANGLER_OUTPUT_FILE_DIRECTORY or WRANGLER_OUTPUT_FILE_PATH.

    For example for an npm Astro project these would be:

    • Framework id: astro
    • Build command: npm run build
    • Deploy command: npx wrangler deploy

    While for a Next.js project they would instead be:

    • Framework id: next
    • Build command: npx @​opennextjs/cloudflare build
    • Deploy command: npx @​opennextjs/cloudflare deploy
  • #​12211 a5fca2c Thanks @​elithrar! - Remove the 'pubsub' sub-command and related functionality

    The Pub/Sub product was never made publicly available and has been discontinued. This removes the wrangler pubsub command and all associated functionality.

  • Updated dependencies [0c9625a, 0aaf080, b981db5, a113c0d, f7aa8c7]:


Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 04:59 AM, only on Monday ( * 0-4 * * 1 ) in timezone America/Los_Angeles, 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.

@pkg-pr-new
Copy link

pkg-pr-new bot commented Feb 9, 2026

Open in StackBlitz

npm i https://pkg.pr.new/get-convex/polar/@convex-dev/polar@40

commit: def331e

@renovate renovate bot merged commit 039d04b into main Feb 9, 2026
3 checks passed
@renovate renovate bot deleted the renovate/routine-updates branch February 9, 2026 12:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants