Approvals

Approvals is the inbox of plugin updates fetched from upstream (uMod) that wait for a decision. "Updates fetched from upstream (uMod) wait here. Nothing is installed before you approve. Scan warnings are hints, they never block." Capability: operations. A badge on the sidebar entry counts what is waiting.

How updates arrive

Plugins with an upstream address are checked on uMod. A new file creates a pending release; it appears here. The checker runs once a day (05:15 UTC) when the platform has automatic checks on, and staff can run it on demand.

Check for updates

Button	Effect
Check for updates (Approvals and Plugin catalog)	Queues a check of every plugin. "Checking every plugin on uMod. New versions show up in Plugin Approvals."
Check uMod (plugin page, and a server's Plugins tab)	Checks one plugin now.

Results: "New version found: it waits in Plugin Approvals", "Up to date with uMod", "Nothing new on uMod", "This plugin has no uMod source", or "uMod now serves a different plugin class: ignored" (a plugin that changes its class is never accepted as an update). Checks are rate limited: one per plugin per 60 seconds, all plugins once per 10 minutes, and uMod's own retry delay; a blocked click says "Checked recently: try again in time."

Review an update

Each card shows the plugin name, origin, auto rollout (when the plugin's policy starts a rollout on approval), the current and new version, the size, SHA, the upstream URL and the date.

• Scan warnings: the source is scanned for suspicious patterns; each warning gives the rule, the line and a snippet. They are hints only.
• Click Review to see the source diff against the current release.

Approve

1. Tick Start a rollout after approving (not shown when the policy is already auto).
2. Click Approve. The release becomes the latest approved release; with the tick, or with an auto policy, a rollout starts.

Reject

Click Reject, write the Reason (required, up to 500 characters) and Confirm reject. The release is marked rejected and is never installed.

Rules

• Only platform staff approve or reject. Community admins cannot.
• Approving does not touch a server by itself; servers change through a rollout or when a community picks the version.
• If the plugin class changed upstream, the update is ignored instead of queued.

Troubleshooting

Problem	Fix
"No updates waiting"	Nothing new, or the checker has not run: use Check for updates.
"Approvals are not available on this backend"	The platform has the feature switched off.
"Checked recently"	Wait; limits protect uMod.