Versioning
Publish updates, manage release channels, write release notes, and handle bad releases.
Release Channels
Each version belongs to one of two channels:
Stable
Shown to all buyers. This is the version used for the "Download" button on the product page by default. Buyers are notified by email when a new stable version is published.
Beta
Visible to all buyers but not the default download. Use beta for testing features before a stable release. No buyer email notification is sent for beta versions.
Release Notes
Release notes are required for every version. Write them in the rich-text editor on the New Version page. Good release notes include:
- A bulleted list of what changed
- Any breaking changes or migration steps
- Bug fixes with reference numbers if you use issue tracking
Release notes are shown on the product page (expand a version row to read them) and in the changelog timeline below the versions table.
Yanking a Version
What is yanking?
Yanking marks a version as unavailable. Yanked versions are hidden from the versions table on the product page and cannot be downloaded by buyers. Existing downloads of the file are not affected — the files are not deleted.
You must provide a reason when yanking. The reason is shown to buyers who already have that version in their order history.
When to yank
- A critical bug was discovered that could corrupt data or crash servers
- A security vulnerability was found in that specific release
- The version was published to the wrong channel by mistake
Restoring a yanked version
You can "restore" a yanked version at any time from the Version History page. This makes it available for download again.
File Limits
Plugin files must be under 50 MB. Accepted formats:
.jar— Java plugins (Minecraft Bukkit/Paper/Spigot).zip— multi-file plugins, resource packs, or mixed bundles.dll— Rust/uMod plugins
Files are stored on S3-compatible object storage and served via CDN.