Pattern strings / tokens

When setting up patterned strings in Runway to define your team’s naming conventions around branch names, tags, or feature affiliations, you can optionally use tokens to allow for dynamic naming conventions that depend on the release’s version, build numbers, etc.

Available token types

• {version} — three-segment SemVer

  • Example: 1.2.3

• {versionConcise} — allows for a three-, two- or one-segment SemVer

  • Example: 1.2.3

  • Example: 1.2

  • Example 1

• {releaseName} — human-readable release name

  • Example: Cinnamon

  • Example: BigFeature

• {appStoreBuildNumber} — build number as it appears in App Store Connect or Play Console

• {ciBuildNumber} — build number as it appears in CI

Usage

Tags

• Required:

  • either {version} or {versionConcise}

• Not allowed:

  • None — all available token types are allowed

Feature affiliations

• Required:

  • At least one of {version}, {versionConcise}, and {ReleaseName}

• Not allowed:

  • {appStoreBuildNumber} and {ciBuildNumber}

Branch

• If branch is versioned (i.e. branches are created per release)

  • Required:

    • either {version}, {versionConcise}, or {ReleaseName}

  • Not allowed:

    • {appStoreBuildNumber} and {ciBuildNumber}

• If branch is static (same across all releases)

  • No token types are allowed