cuelang.org/go@v0.10.1/internal/ci/repo/repo.cue (about)

     1  // package repo contains data values that are common to all CUE configurations
     2  // in this repo. The list of configurations includes GitHub workflows, but also
     3  // things like gerrit configuration etc.
     4  package repo
     5  
     6  import (
     7  	"cuelang.org/go/internal/ci/base"
     8  )
     9  
    10  base
    11  
    12  githubRepositoryPath: "cue-lang/cue"
    13  
    14  unityRepositoryPath: "cue-unity/unity-private"
    15  unityRepositoryURL:  "https://github.com/" + unityRepositoryPath
    16  
    17  cuelangRepositoryPath: "cue-lang/cuelang.org"
    18  
    19  defaultBranch:        _
    20  releaseBranchPrefix:  "release-branch."
    21  releaseBranchPattern: releaseBranchPrefix + "*"
    22  protectedBranchPatterns: [defaultBranch, releaseBranchPattern]
    23  
    24  botGitHubUser:      "cueckoo"
    25  botGitHubUserEmail: "cueckoo@gmail.com"
    26  
    27  linuxMachine:   "ubuntu-22.04"
    28  macosMachine:   "macos-14"
    29  windowsMachine: "windows-2022"
    30  
    31  // Use the latest Go version for extra checks,
    32  // such as running tests with the data race detector.
    33  // This may be a release candidate if we are late into a Go release cycle.
    34  latestGo: "1.23.x"
    35  
    36  // The list of all Go versions that we run our tests on.
    37  // This typically goes back one major Go version, as we support two at a time.
    38  matrixGo: ["1.22.x", latestGo]
    39  
    40  // Use a specific latest version for release builds.
    41  // Note that we don't want ".x" for the sake of reproducibility,
    42  // so we instead pin a specific Go release.
    43  pinnedReleaseGo: "1.23.2"
    44  
    45  goreleaserVersion: "v2.0.1"
    46  
    47  // zeroReleaseTagSuffix is the suffix used to identify all "zero" releases.
    48  // When we create a release branch for v0.$X.0, it's likely that commits on the
    49  // default branch will from that point onwards be intended for the $X+1
    50  // version. However, unless we tag the next commit after the release branch, it
    51  // might be the case that pseudo versions of those later commits refer to the
    52  // $X release.
    53  //
    54  // A "zero" tag fixes this when applied to the first commit after a release
    55  // branch. Critically, the -0.dev pre-release suffix is ordered before -alpha.
    56  // tags.
    57  zeroReleaseTagSuffix: "-0.dev"
    58  
    59  // zeroReleaseTagPattern is the GitHub glob pattern that corresponds
    60  // zeroReleaseTagSuffix.
    61  zeroReleaseTagPattern: "*" + zeroReleaseTagSuffix
    62  
    63  codeReview: "cue-unity": unityRepositoryURL