Collections documentatation - Add information about semantic versioning (#60969)
This commit is contained in:
parent
229219ab77
commit
543401f83b
1 changed files with 6 additions and 0 deletions
|
@ -267,6 +267,12 @@ Once you upload a version of a collection, you cannot delete or modify that vers
|
|||
uploading. The only way to change a collection is to release a new version. The latest version of a collection (by highest version number)
|
||||
will be the version displayed everywhere in Galaxy; however, users will still be able to download older versions.
|
||||
|
||||
Collection versions use `Sematic Versioning <https://semver.org/>` for version numbers. Please read the official documentation for details and examples. In summary:
|
||||
|
||||
* Increment major (for example: x in `x.y.z`) version number for an incompatible API change.
|
||||
* Increment minor (for example: y in `x.y.z`) version number for new functionality in a backwards compatible manner.
|
||||
* Increment patch (for example: z in `x.y.z`) version number for backwards compatible bug fixes.
|
||||
|
||||
Migrating Ansible content to a collection
|
||||
=========================================
|
||||
|
||||
|
|
Loading…
Reference in a new issue