17b60f1f5a
Change-Id: I0c60698f5277c500fad1c85b212565adca39e3c8 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/81207 Commit-Queue: Lily Chen <chlily@google.com> Reviewed-by: Lily Chen <chlily@google.com> Auto-Submit: David Benjamin <davidben@google.com>
2.2 KiB
Cutting Periodic "Releases"
The Bazel Central Registry needs versioned snapshots and cannot consume git revisions directly. To cut a release, do the following:
-
Pick a new version. The current scheme is
0.YYYYMMDD.0. If we need to cut multiple releases in one day, increment the third digit. -
Update
MODULE.bazelwith the new version and upload to Gerrit. -
Once that CL lands, make a annotated git tag at the revision. This can be done from Gerrit. The "Annotation" field must be non-empty. (Just using the name of the tag again is fine.)
-
Wait for the tag to be mirrored to GitHub. If this takes too long, fetch the tag in your local checkout and push it by hand. (
git fetch originfollowed bygit push github NAME_OF_TAG, ifgithubis the name of the remote in your checkout.) -
Download the tarball of the tag from GitHub using the "tar.gz" link.
-
Create a corresponding GitHub release. You have to be an owner of GitHub repository for this to work. Ask in the team chat if it does not work. Attach the tarball to the release. (The
prepare_bcr_moduletool will check that this was correct.) -
Clone a copy of https://github.com/bazelbuild/bazel-central-registry so that you can make a GitHub pull request against it.
-
Run
go run ./util/prepare_bcr_module TAGand follow the instructions. The tool does not require special privileges, though it does fetch URLs from GitHub and read the local checkout. It outputs a JSON file for BCR's tooling to consume. The instructions will tell you to run a bazelisk command. -
CD into the root of your bazel-central-registry fork, and run the bazelisk command indicated by the script output above. It will add a directory to the repository which is untracked, use
git statusto find it, andgit addto add it to what you are about to commit. Then commit the changes and added directory, and submit it as a pr to bazel-central-registry.