Skip to content

chore(deps): update rust crate notify to v9 - #16741

Closed
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/notify-9.x
Closed

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/notify-9.x

Conversation

@renovate

@renovate renovate Bot commented Nov 21, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
notify workspace.dependencies major 8.2.0 → 9.0.0

Release Notes

notify-rs/notify (notify)

v9.0.0: notify: v9.0.0

Compare Source

No significant change since v9-rc, see https://github.com/notify-rs/notify/blob/main/docs/UPGRADING_V8_TO_V9.md for details.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@codspeed

codspeed Bot commented Nov 21, 2026 •

Copy link
Copy Markdown
Contributor

Merging this PR will degrade performance by 0.24%

2 warnings, 1 note

⚠️ 120 benchmarks are dominated by system calls

System calls cannot be simulated consistently and are left out of the measure. The reported value understates the real cost. Switch to the Walltime instrument to measure them.

Learn more about system calls

See affected benchmarks

⚠️ 2 benchmarks with a significant change ran on different hardware

Their base and head results were measured on machines with a different CPU, core count or memory, so the changes might not come from the code. Run base and head on the same runner type.

Learn more about Macro Runners

See affected benchmarks

ℹ️ 1 benchmark has no flamegraph

The flamegraph wasn't generated: most of the time was spent in runtime internals, which would leave nothing useful to analyze.

See affected benchmarks

⚡ 1 improved benchmark
❌ 1 regressed benchmark
✅ 411 untouched benchmarks
⏩ 70 skipped benchmarks1

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

Mode Benchmark BASE HEAD Efficiency
❌ CPU Simulation ls_recursive_deep_tree[(200, 2)] 2.8 ms 2.9 ms -3.79%
⚡ CPU Simulation ls_recursive_mixed_tree 2.5 ms 2.4 ms +3.45%

Tip

Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.


Comparing renovate/notify-9.x (6a310e0) with main (f21dd53)

Open in CodSpeed

Footnotes

  1. 70 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

@renovate
renovate Bot force-pushed the renovate/notify-9.x branch from 379e8e7 to 6a310e0 Compare November 21, 2026 07:53
@xtqqczze

Copy link
Copy Markdown
Collaborator

Superseded by #16620.

@xtqqczze xtqqczze closed this Nov 21, 2026
@renovate

renovate Bot commented Nov 21, 2026

Copy link
Copy Markdown
Contributor Author

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 9.x releases. But if you manually upgrade to 9.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate
renovate Bot deleted the renovate/notify-9.x branch November 21, 2026 11:13
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.

1 participant