commit | 98948362ff1bf39ffb302284b80f7cfa90bfb72a | [log] [tgz] |
---|---|---|
author | Yun Peng <pcloudy@google.com> | Tue Nov 08 16:14:20 2022 +0100 |
committer | GitHub <noreply@github.com> | Tue Nov 08 16:14:20 2022 +0100 |
tree | 94217dbe2dfc5eb715dcc3caea019feefc8548eb | |
parent | 7298c862dd3a2446a5eb360ad626b693dcf7edb6 [diff] |
Prevent the publish bazel binary pipeline from stamping Bazel version in the binaries (#1491) In https://github.com/bazelbuild/continuous-integration/pull/1195 we add `--stamp --embed_label=<version>` by parsing the branch name to fix https://github.com/bazelbuild/bazel/issues/13712. This is also causing the https://buildkite.com/bazel-trusted/publish-bazel-binaries pipeline to publish binaries with version stamp from commits in release branches. This could be confusing, because commits from `release-6.0.0` will always have version `6.0.0`. This PR tries to prevent that.