Update all patch versions

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	Pending	Age	Confidence
cargo-nextest	workspace.dependencies	patch	0.9.144 → 0.9.145
daisyui (source)	devDependencies	patch	5.7.37 → 5.7.38	5.7.42 (+3)
eslint-plugin-react-refresh	devDependencies	patch	0.5.6 → 0.5.7

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

nextest-rs/nextest (cargo-nextest)

v0.9.145: cargo-nextest 0.9.145

Compare Source

Changed

• Configuration diagnostics now name the file each setting came from. For example, cargo nextest show-config version shows which file specified the nextest-version requirement, and cargo nextest show-config test-groups shows which file each override was defined in.

  For now, this is most useful when tool-specific config files are in play, but upcoming work to support local configuration files also benefits from this. (#​3580, #​3584)

• Config file paths in errors and warnings are now displayed relative to the directory nextest is invoked from, following typical CLI conventions. Previously, parse errors showed absolute paths and warnings showed paths relative to the workspace root. In stylized output, config file paths are now colored as well. (#​3568, #​3570, #​3577)

Fixed

• Per-test overrides and setup and wrapper scripts defined in a profile's inheritance chain are now applied. Previously, only the selected profile's own overrides and those in profile.default were consulted, so overrides in intermediate profiles were silently skipped. As part of this change, a profile that does not set default-filter now inherits it from the nearest ancestor that does, rather than always from profile.default. (#​3585)

• A default-filter set by a tool config file is now respected when the repository config does not set one. Previously, the tool's filter was ignored and all() was used. (#​3592)

• Profile inheritance cycles that span multiple config files, such as a tool config file redefining a profile that the repository config inherits from, are now detected and reported as errors. Previously, cycles were only detected within a single file. (#​3588)

• Passing --tool-config-file more than once for the same tool name now produces an error. Previously, nextest panicked internally. (#​3589)

• The hint shown when a command requires an experimental feature that isn't enabled now points at the correct config file path when nextest is run from a subdirectory of the workspace, from outside the workspace, or with an explicit --config-file. (#​3565)

• On Unix platforms where the Rust standard library cannot create pipes with FD_CLOEXEC set atomically (most notably Apple platforms), a test could inherit a sibling test's capture pipe if the two were spawned concurrently. The sibling was then reported as having leaked handles after it exited. Nextest now creates capture pipes itself and coordinates pipe creation with process spawning, so that spawns no longer inherit stray pipes. (#​3553)

  An upcoming design document will go over how nextest spawns processes in detail, including more information about this workaround.

  Thanks gaborbernat for your first contribution!

saadeghi/daisyui (daisyui)

v5.7.38

Compare Source

Bug Fixes

• style aria-current as active in dock (#​4753) (fe22841)
• style aria-current as menu-active in menu (#​4752) (10dc2fb)
• style aria-pressed and aria-current as btn-active in button (#​4754) (8e495a0)

ArnaudBarre/eslint-plugin-react-refresh (eslint-plugin-react-refresh)

v0.5.7

Compare Source

Add allowCompoundComponents option (#​117)

Default: false (true in vite config)

Don't warn when components are exported as an object gathering them. Every member of the object must be a component, and a member holding an anonymous function requires a component name as key.

This should be enabled if the fast refresh implementation correctly handles this case. Vite supports it since @vitejs/plugin-react 4.7.0, @vitejs/plugin-react-swc 3.11.0.

{
  "react-refresh/only-export-components": [
    "error",
    { "allowCompoundComponents": true }
  ]
}

Enabling this option allows code such as the following:

const Root = () => <></>;
const Label = () => <></>;
export const Tag = { Root, Label };

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "before 8am every weekday"
• 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.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.6%. Comparing base (e3420a8) to head (5fbea07).

Additional details and impacted files

@@          Coverage Diff          @@
##            main   #1773   +/-   ##
=====================================
  Coverage   83.6%   83.6%           
=====================================
  Files        137     137           
  Lines      13343   13343           
=====================================
+ Hits       11156   11158    +2     
+ Misses      2187    2185    -2     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[opentelemetry-pr-dashboard]

Pull request dashboard status

Merged · refreshed 2026-09-18 12:21 UTC

Status above doesn't look right?

• Anything look wrong? Report it with what you expected; it helps us improve the dashboard.