fix(ntfy): save priority field as number instead of string

[gauthier-th]

Description

Because the priority field of the ntfy.sh settings was set using a HTML , the saved value was a string instead of the expected number. This PR converts the string value of the into a number.

• Fixes ntfy notifications not working #2929

How Has This Been Tested?

Send a test notification with a priority set.

Screenshots / Logs (if applicable)

N/A

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

• New Features

  • Added priority and locale configuration options for ntfy notifications.

• Bug Fixes

  • Fixed priority value type handling in ntfy notification settings.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 28df7683-2e86-4d93-ad0f-9b74e7767ae8

📥 Commits

Reviewing files that changed from the base of the PR and between c04172a and e798d9d.

📒 Files selected for processing (2)

• seerr-api.yml
• src/components/Settings/Notifications/NotificationsNtfy/index.tsx

---

📝 Walkthrough

Walkthrough

The PR fixes ntfy notification failures by ensuring the priority field is transmitted as a number rather than a string. The OpenAPI schema is extended to document priority and locale fields, and the frontend component coerces the form value to a number in both settings save and test notification requests.

Changes

Ntfy Notification Priority Fix

Layer / File(s)	Summary
API Schema Extension seerr-api.yml	OpenAPI schema adds priority (number) and locale (string) fields to NtfySettings.options to document the expected request structure.
Frontend Priority Type Coercion src/components/Settings/Notifications/NotificationsNtfy/index.tsx	Settings form submission and test notification submission both coerce values.priority to a number via Number() before sending to the ntfy API to match the numeric schema requirement.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Suggested reviewers

• fallenbagel
• 0xSysR3ll

Poem

A rabbit hops through the JSON streams,
Where priority numbers fill the dreams,
No more strings to twist and bend,
The ntfy notifications mend! 🐰✨

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The PR title accurately describes the main change: converting the ntfy priority field from string to number before saving, which directly addresses the issue.
Linked Issues check	✅ Passed	The PR fixes the JSON serialization error in issue #2929 by converting priority to a number type, aligning with the API schema and resolving the invalid JSON request body error.
Out of Scope Changes check	✅ Passed	All changes are directly scoped to fixing the ntfy priority issue: OpenAPI schema updates, type coercion in the component, and no unrelated modifications.

_{✏️ Tip: You can configure your own custom pre-merge checks in the 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 and usage tips.}