Releases
Manage versions and releases of your packages.
Overview
Releases represent specific versions of your package that customers can install. Each release has a version number, release date, and the package source code.
Version Numbering
Privato follows Semantic Versioning (SemVer). Version numbers should be in the format:
MAJOR.MINOR.PATCH
For example: 1.0.0, 1.2.3, 2.0.0-beta.1
Pre-release Versions
You can create pre-release versions using suffixes:
1.0.0-alpha.1- Alpha releases1.0.0-beta.1- Beta releases1.0.0-rc.1- Release candidates
Creating Releases
If you've connected your GitHub repository, releases are created automatically when you create a release in GitHub.
Privato will detect the new release and sync the data into the private Composer registry.
Release Visibility
Releases are controlled by release channels. A customer can only install releases that their license's release channel allows.
Yanking Releases
Yanking isn't currently available during the public beta but will be implemented in the near future.