You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 1, 2022. It is now read-only.
This issue describes the idea behind Semantha's versioning logic.
Presumptions
The defined master branch is a basis for all other branches - all prereleases consider master as the only source of truth, regardless of the previous pre-releases.
All relevant tags follow package_name@package_version tagging format.
Package versions follow semantic versioning where pre-releases state the target master version and iteration of the prerelease (ie. semantha-core@v1.0.2-beta.2- this is the second iteration of code for 1.0.2 release)
Arguments
prerelease tag (defaults to none - master),
package name.
Idea
The algorithm crawls through the existing repository tags. Each tag is examined to match the name of the package. The algorithm is repeated/paginates through the results until it finds a matching prerelease tag or a master release.
Code
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Presumptions
master
branch is a basis for all other branches - all prereleases considermaster
as the only source of truth, regardless of the previous pre-releases.package_name@package_version
tagging format.semantha-core@v1.0.2-beta.2
- this is the second iteration of code for1.0.2
release)Arguments
Idea
The algorithm crawls through the existing repository tags. Each tag is examined to match the name of the package. The algorithm is repeated/paginates through the results until it finds a matching prerelease tag or a master release.
Code
The text was updated successfully, but these errors were encountered: