Rebuild paid plugins in Satis on every push

[simonhamp]

A push to a plugin's repo only refreshed its metadata on the site. Satis builds only ran on a published release, the Sync to Satis button, or satis:build. Satis publishes every branch as dev-<branch>, but that only helps if a build actually runs. So new commits on main and new WIP branches weren't installable until someone cut a release.

You can see it on plugins.nativephp.com right now. main on mobile-firebase and mobile-biometrics has commits from 3 September that were never published. Four branches on mobile-geolocation, mobile-firebase and mobile-biometrics are missing completely.

Now a push from either webhook (the per-repo one or the GitHub App) queues a new BuildPluginInSatis job for that plugin. The job waits a minute and is unique per plugin until it starts, so a burst of pushes shares one build. Satis reads the repo when it builds, so that one build picks up everything. Deleted branches drop out on the next build too.

Things to check:

• It runs for every paid plugin, not just first-party ones. Third-party branches were already being published, they were just stale. Narrowing it to isOfficial() is a one-line change in Plugin::queueSatisRebuild().
• Free plugins and drafts are skipped. Building a free plugin would put it in Satis and override its Packagist listing. Drafts haven't been submitted, and plugins only enter Satis on submission.
• A release now usually means two builds. SyncPluginReleases builds straight away, and the tag's push queues another one a minute later. That's harmless, just redundant.
• Satis will build more often. Every build on the Satis server uses the same build directory, so it's worth confirming its queue runs a single worker.
• After deploying, branches already out of date catch up on each repo's next push. Running php artisan satis:build once catches everything up straight away.

Tests: the targeted webhook and Satis tests pass (61). The full suite passed (2025, 1 skipped for missing local config) before a final small change that added the draft check. I re-ran the targeted tests after that change.

🤖 Generated with Claude Code