v5.0.3

2026-08-25clean-release

A release-pipeline reliability patch: the same code as 5.0.2, shipped through a clean, properly-tagged release.

Highlights

01
No library changes
5.0.3 is byte-for-byte the same library as 5.0.2 — same interrupt-flag hygiene, same bounded client closes. If you are already on 5.0.2 there is nothing new to adopt. This release exists purely to fix the publishing pipeline that shipped 5.0.2 to Maven Central but left the pipeline red and its release job skipped (no git tag, no release entry).
02
Central publishing no longer blocks on the portal queue
The Central publish step now completes as soon as Sonatype accepts the bundle (waitUntil=uploaded with autoPublish=true) rather than polling until the portal finishes its publish queue. Previously a slow portal queue could expire the plugin's polling window after the artifacts were already accepted — a green publish reported as a red job.
03
The AI skill-pack mirror check tolerates edge propagation
The R2 mirror upload is verified through its public URL with retry-and-backoff, so the few seconds a brand-new object takes to propagate to the Cloudflare edge no longer fails the release. A genuinely unreachable mirror still fails, just not a transient lag.

Central publishing uses waitUntil=uploaded (with autoPublish=true) instead of waitUntil=published, so the release job succeeds once the bundle is accepted and the portal publishes asynchronously. Under waitUntil=published the plugin's polling window could expire while the portal was still queued — which published 5.0.2 to Maven Central but left the pipeline red and skipped the release job. Build/CI only; no change to the published artifacts.
The publish:skills:r2 job now retries the public-URL reachability check with backoff (~1 minute) before failing, so Cloudflare edge propagation of a brand-new key no longer fails the release while a genuinely broken mirror still does. Build/CI only.