Skip to content

Comments

fix(deps): update minor updates#2157

Merged
rocketstack-matt merged 1 commit intomainfrom
renovate/minor-updates
Feb 23, 2026
Merged

fix(deps): update minor updates#2157
rocketstack-matt merged 1 commit intomainfrom
renovate/minor-updates

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 23, 2026 •
edited
Loading

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Type Update Pending
@mermaid-js/layout-elk ^0.1.9 → ^0.2.0 age confidence dependencies minor
eslint-plugin-react-refresh ^0.4.20 → ^0.5.0 age confidence devDependencies minor 0.5.1
eslint-plugin-react-refresh ^0.4.19 → ^0.5.0 age confidence devDependencies minor 0.5.1
lucide-react (source) ^0.562.0 → ^0.564.0 age confidence dependencies minor 0.575.0 (+10)
node (source) 22.14.0 → 22.22.0 age confidence minor
rollup (source) 4.54.0 → 4.57.1 age confidence overrides minor 4.59.0 (+1)
rollup (source) 4.54.0 → 4.57.1 age confidence resolutions minor 4.59.0 (+1)
org.owasp:dependency-check-maven (source) 12.1.9 → 12.2.0 age confidence build minor
org.apache.maven.plugins:maven-compiler-plugin (source) 3.14.1 → 3.15.0 age confidence build minor
io.quarkus:quarkus-bom 3.30.6 → 3.31.3 age confidence import minor 3.32.0 (+1)
io.quarkus:quarkus-maven-plugin 3.30.6 → 3.31.3 age confidence build minor 3.32.0 (+1)

Release Notes

mermaid-js/mermaid (@​mermaid-js/layout-elk)

v0.2.0

Compare Source

Minor Changes
Patch Changes
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"] }]
}
lucide-icons/lucide (lucide-react)

v0.564.0: Version 0.564.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@0.563.1...0.564.0

v0.563.0: Version 0.563.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@0.562.0...0.563.0

nodejs/node (node)

v22.22.0: 2026-01-13, Version 22.22.0 'Jod' (LTS), @​marco-ippolito

Compare Source

This is a security release.

Notable Changes

lib:

  • (CVE-2025-59465) add TLSSocket default error handler
  • (CVE-2025-55132) disable futimes when permission model is enabled
    lib,permission:
  • (CVE-2025-55130) require full read and write to symlink APIs
    src:
  • (CVE-2025-59466) rethrow stack overflow exceptions in async_hooks
    src,lib:
  • (CVE-2025-55131) refactor unsafe buffer creation to remove zero-fill toggle
    tls:
  • (CVE-2026-21637) route callback exceptions through error handlers
Commits

v22.21.1: 2025-10-28, Version 22.21.1 'Jod' (LTS), @​aduh95

Compare Source

Commits

v22.21.0: 2025-10-20, Version 22.21.0 'Jod' (LTS), @​aduh95

Compare Source

Notable Changes
  • [1486fedea1] - (SEMVER-MINOR) cli: add --use-env-proxy (Joyee Cheung) #​59151
  • [bedaaa11fc] - (SEMVER-MINOR) http: support http proxy for fetch under NODE_USE_ENV_PROXY (Joyee Cheung) #​57165
  • [af8b5fa29d] - (SEMVER-MINOR) http: add shouldUpgradeCallback to let servers control HTTP upgrades (Tim Perry) #​59824
  • [42102594b1] - (SEMVER-MINOR) http,https: add built-in proxy support in http/https.request and Agent (Joyee Cheung) #​58980
  • [686ac49b82] - (SEMVER-MINOR) src: add percentage support to --max-old-space-size (Asaf Federman) #​59082
Commits

v22.20.0: 2025-09-24, Version 22.20.0 'Jod' (LTS), @​richardlau

Compare Source

Notable Changes
OpenSSL updated to 3.5.2

For official Node.js builds, or builds using the default build configuration, Node.js now bundles OpenSSL 3.5.2. This update allows Node.js 22.x to be supported through to the planned End-of-Life date of 2027-04-30 as the previously bundled OpenSSL 3.0.x goes out of support in September 2026.

This change does not affect third-party builds of Node.js that link to an external OpenSSL (or OpenSSL-compatible) library.

Other notable changes
Commits

Configuration

📅 Schedule: Branch creation - "before 7am on monday" in timezone 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 requested a review from a team as a code owner February 23, 2026 04:47
@rocketstack-matt rocketstack-matt merged commit 3a4d952 into main Feb 23, 2026
22 checks passed
@rocketstack-matt rocketstack-matt deleted the renovate/minor-updates branch February 23, 2026 12:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@rocketstack-matt rocketstack-matt rocketstack-matt approved these changes

Assignees

No one assigned

Labels

calm-hub The Calm Hub Product calm-hub-ui cli config shared

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@rocketstack-matt