Content Versioning

What's a Version?

A version is simply a tag created in a repository, where the tag name matches the semantic version format.

If the repository exists on GitHub, the easiest way to create a tag is to create a new release. As you create the release, you'll be asked to name the tag. Follow the Semantic Versioning Spec when setting the name.

Valid tag examples, include:

• 1.0.0
• 1.0.1
• 1.0.0-beta.11
• 1.0.0-rc.1
• v1.0.0
• V1.0.0

Version Rules

Versions:

• Exist on the repository only, not on or within individual content objects
• Apply to all content contained within the repository
• Must fit the semantic versioning format

Versions and Galaxy Import

The Galaxy import process will do the following:

• Inspect tags on a repository, and import those that match the semantic version format
• Issue a warning for tags that don't match
• In Galaxy's UI, tags will be surfaced without the leading 'v' or 'V', and will be sorted in descending order, with the newest version appearing first.

NOTE In a future release of Galaxy server, content repositories without semantic version tags will not be imported, and the import process will only index content items associated with the latest version.

Versions in Galaxy CLI

The Galaxy CLI install command supports versions, allowing the user to specify a version when installing all content from a repository, all content of a specific type, or a specific content object.

When providing a version, provide the semantic version with or without the leading 'v' or 'V'. The client will match this to a tag, download the corresponding archive file from the SCM platform, and install the requested content.

For specific examples of passing version to the install command, view Install Use Cases