Releases are how your customers can update to the latest version of your product. Learn more about creating a new release.
Major releases should be used when new features are developed. Depending on your version scheme, this could be either a 1.0 → 2.0 or a 1.1.0 → 1.2.0 release. Customers will be reminded to create a backup before updating.
Minor releases are for bug fixes or feature tweak releases. This could represent a version change of 1.0 → 1.1 or 1.0.0 → 1.0.1. A minor release should not have breaking changes, and should be a simple update for your customers.
Whenever a vulnerability is fixed a security release should be created. The security message can be used to inform your customers about the urgency of the update.
Pre-releases can be used to offer beta versions of your software to your customers. Customers need to opt-in to the pre-release track when activating their license key. Pre-releases won’t appear in the changelog.
You MUST version these releases using semantic versioning to ensure updates are properly deployed. For example to release a beta for version 1.2, your releases should be versioned 1.2-beta.