• Home
  • Line#
  • Scopes#
  • Navigate#
  • Raw
  • Download
1# Cutting Periodic "Releases"
2
3The [Bazel Central Registry](https://github.com/bazelbuild/bazel-central-registry)
4needs versioned snapshots and cannot consume git revisions directly. To cut a
5release, do the following:
6
71. Pick a new version. The current scheme is `0.YYYYMMDD.0`. If we need to cut
8   multiple releases in one day, increment the third digit.
9
102. Update `MODULE.bazel` with the new version and upload to Gerrit.
11
123. Once that CL lands, make a annotated git tag at the revision. This can be
13   [done from Gerrit](https://boringssl-review.googlesource.com/admin/repos/boringssl,tags).
14   The "Annotation" field must be non-empty. (Just using the name of the tag
15   again is fine.)
16
174. Wait for the tag to be mirrored to GitHub, and create a corresponding
18   GitHub [release](https://github.com/google/boringssl/releases/new). You
19   have to be a boringssl owner on github for this to work, if it the new link
20   does not work, bug davidben to invite you to the repository.
21
225. Download the "Source code (tar.gz)" archive from the new release and
23   re-attach it to the release by clicking the edit button, and selecting "Attach New File"
24   overtop of the release artifacts in github.  (The next step will check that the archive is
25   correct.)
26
276. Clone a copy of https://github.com/bazelbuild/bazel-central-registry so that you
28   can make a github pull request against it.
29
306. Run `go run ./util/prepare_bcr_module TAG` and follow the instructions. The
31   tool does not require special privileges, though it does fetch URLs from
32   GitHub and read the local checkout. It outputs a JSON file for BCR's tooling
33   to consume. The instructions will tell you to run a bazelisk command.
34
357. CD into the root of your bazel-central-registry fork, and run the bazelisk
36   command indicated by the script output above. It will add a directory to the
37   repository which is untracked, use "git status " to find it, and "git add" to
38   add it to what you are about to commit.  Then commit the changes and added
39   directory, and submit it as a pr to bazel-central-registry.
40