[fallenbagel]

Description

StatusChecker polls /api/v1/status?checkUpdateAvailable=false on a 60 second interval, and that subscription derives the server restart required modal. The network and general settings forms called mutate on these after saving a reqstart-required field, a bare key that predates the checkUpdateAvailable query param in #3137 put on StatusChecker's key. SWR matches keys by exact string, so that mutate no longer touched the subscription it was meant to refresh and the modal only appeared on the next poll, up to a minute later. Both call sites no mutate the key that it actually holds.

This was accidentally added to #3375 as 4d414ba instead of #3368

How Has This Been Tested?

(no need)

Screenshots / Logs (if applicable)

Checklist:

• I have read and followed the contribution guidelines.
• Disclosed any use of AI (see our policy)
• I have updated the documentation accordingly.
• All new and existing tests passed.
• Successful build pnpm build
• Translation keys pnpm i18n:extract
• Database migration (if required)

Summary by CodeRabbit

• Bug Fixes
  • Improved status refresh behavior after saving main or network settings.
  • Prevented unnecessary update-availability checks during these refreshes, providing a smoother settings-saving experience.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: d4907aa3-5181-4470-be91-c02d471d30e4

📥 Commits

Reviewing files that changed from the base of the PR and between 92f8404 and 2e262e7.

📒 Files selected for processing (2)

• src/components/Settings/SettingsMain/index.tsx
• src/components/Settings/SettingsNetwork/index.tsx

Included review availability: Your plan provides up to 10 included reviews per hour; 8 remain after this review.

---

📝 Walkthrough

Walkthrough

Main and network settings now refresh status through /api/v1/status?checkUpdateAvailable=false after saving. This disables update-availability checks during both refresh operations.

Changes

Settings status refresh

Layer / File(s)	Summary
Post-save status refresh src/components/Settings/SettingsMain/index.tsx, src/components/Settings/SettingsNetwork/index.tsx	Both settings save flows now revalidate status with checkUpdateAvailable=false.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 2e262

This PR makes two localized query-key updates so settings changes refresh the restart-required modal immediately; no actionable merge-blocking risk remains after normal checks and review.

Suggested reviewers: 0xsysr3ll, danshilm

Poem

A rabbit checks the settings bright
No update search disturbs the night
Main saves hop, network too
Status refreshes clean and true
With quiet paws, the work is through

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
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.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes updating the status query-string key so the restart-required modal appears immediately after saving settings.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}