GitVersion.yml

assembly-versioning-format: '{Major}.{Minor}.{WeightedPreReleaseNumber}'
assembly-informational-format: '{Major}.{Minor}{PreReleaseTagWithDash}--{CommitDate}--{ShortSha}'
# GitVersion 5 "ContinuousDeployment" (pre-release number counts commits) is called "ContinuousDelivery" in GitVersion 6
mode: ContinuousDelivery
# JabRef tags two-component versions (v5.15, v6.0-alpha.6); the GitVersion 6 default (Strict) ignores them
semantic-version-format: Loose
# Default strategies minus MergeMessage, which mis-reads old merge commits (e.g. "Merge pull request #7115 from JabRef/hotfix-7114" -> base version 7114.0.0)
strategies: [ConfiguredNextVersion, TaggedCommit, TrackReleaseBranches, VersionInBranchName, Fallback]

branches:
  main:
    regex: ^main
    # Label of the current pre-release phase ("alpha", "beta"); leave empty for a stable release
    label: 'beta'
    # Third component of AssemblySemVer: pre-release-weight + commits since the last tag.
    # The count restarts at every release tag, so each new phase needs a weight above the highest number the previous phase reached
    # (v6.0-alpha.6 + 956 commits reached 34956, hence 50000 for beta). Stay below 60000: GitVersion always uses that for a stable release.
    # Ignored while `label` is empty.
    pre-release-weight: 50000