Skip to content

deps(14): upgrade react-toastify 10 -> 11 - #22

Merged
guarzo merged 1 commit into
mainfrom
deps/14-react-toastify-v11
May 3, 2026
Merged

deps(14): upgrade react-toastify 10 -> 11#22
guarzo merged 1 commit into
mainfrom
deps/14-react-toastify-v11

Conversation

@guarzo

@guarzo guarzo commented May 3, 2026

Copy link
Copy Markdown
Owner

Summary

Bumps react-toastify 10.0 → 11.1 (renderer-only).

Migration notes

Inventoried every call site (8 files): toast.success, toast.error, toast.warning, toast.info, plus a single <ToastContainer> in App.jsx and the react-toastify/dist/ReactToastify.css import.

None of the v11 breaking changes (toast ID handling, containerId option, theme API tweaks) touch our call sites:

  • All call sites use the simple toast.<level>(message) form — no custom IDs, no containerId routing.
  • ToastContainer props in use (position, autoClose, hideProgressBar, newestOnTop, closeOnClick, rtl, pauseOnFocusLoss, draggable, pauseOnHover, theme) all still exist in v11.
  • CSS still exports as dist/ReactToastify.css.

No source changes required.

Test plan

  • npm run test:go — pass
  • npm run test:react — 73/73 pass
  • npm run build:react — built in 799ms
  • Manual: trigger a toast (e.g. login flow, sync) and confirm it renders + dismisses

Summary by CodeRabbit

  • Chores
    • Updated notification library dependency to the latest version.

- react-toastify 10.0 -> 11.1 (renderer)

No source changes required:
- toast.success/error/warning/info call-sites unchanged
- ToastContainer props (position, autoClose, theme, etc.) all
  survived v11
- CSS still imports from react-toastify/dist/ReactToastify.css
@coderabbitai

coderabbitai Bot commented May 3, 2026

Copy link
Copy Markdown

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: a2b2289a-7951-4160-a289-c2659a7277d0

📥 Commits

Reviewing files that changed from the base of the PR and between d95c9c6 and bf0c392.

⛔ Files ignored due to path filters (1)
  • renderer/package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (1)
  • renderer/package.json

📝 Walkthrough

Walkthrough

Updated react-toastify dependency in renderer/package.json from ^10.0.6 to ^11.1.0. No other configuration, scripts, or manifest entries changed.

Changes

Dependency Version Update

Layer / File(s) Summary
Dependency Bump
renderer/package.json
react-toastify version constraint updated from ^10.0.6 to ^11.1.0.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A hop through versions, toast shines bright,
Eleven point one feels just right,
Notifications dance, so very divine,
A simple bump, and all feels fine!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and specifically describes the main change: upgrading the react-toastify dependency from version 10 to 11 in the renderer package.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch deps/14-react-toastify-v11
✨ Simplify code
  • Create PR with simplified code
  • Commit simplified code in branch deps/14-react-toastify-v11

Review rate limit: 4/5 reviews remaining, refill in 12 minutes.

Comment @coderabbitai help to get the list of available commands and usage tips.

@guarzo
guarzo merged commit c805d97 into main May 3, 2026
2 checks passed
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