blender_manifest.toml
Version is read from the manifest on disk — the actual source of truth, not a constant someone forgot to bump.
A complete update pipeline for Blender add-ons. You publish a version; every client that has your add-on installed finds out on its next check.
The master add-on batches the whole library into a single request on startup. One round trip, not one per add-on, and it runs on a background thread so Blender never waits on the network.
Claim your ID once and it is bound to your account. If someone contests it, evidence goes to review rather than to whoever registered first. Verified add-ons carry a badge users can check.
Version spread across your installed base, and how quickly a release is taken up. Enough to know when an old branch can finally be dropped.
Reporters file straight from Blender — traceback pasted, auto-redacted, sent. You get a ticket to triage from the dashboard, duplicates to merge into one thread, and a message in Discord the moment it lands, if you have wired up a webhook.
Version is read from the manifest on disk — the actual source of truth, not a constant someone forgot to bump.
Every installed ID and version goes out together, on an interval you control. Daily by default.
Semantic comparison happens in the registry. Your add-on never reimplements semver.
Where you have uploaded a from→to patch, the client pulls only the delta, straight from the CDN.
Changelog attached, criticality flagged, one click to the download. Nothing installs itself.
One file. Async checks, no blocking, no third-party dependencies.
One endpoint returns version, changelog, and update URL.
Reads blender_manifest.toml directly.
Decide how often clients check. Daily by default.
No account for the reporter — a ticket they can poll for your status and note.
Wire a webhook once; every new report pings the channel with the excerpt, ticket, and versions.
Users see what changed before deciding to update.
Mark a release users should not skip.
Ship a delta instead of the whole archive.
Prove an add-on is genuinely yours.
Revoke and regenerate from the dashboard at any time.
Unregistered add-ons still get version tracking from independent sources.
No personal data is collected from the people running your add-on.
No tiers, no seat counts, no card on file.