xref: /aosp_15_r20/external/bazelbuild-rules_testing/RELEASING.md (revision d605057434dcabba796c020773aab68d9790ff9f)
1# Releases
2
3Releases are mostly automated and triggered by adding a tag:
4
5Assuming you have a remote named `upstream` pointing to the repo:
6
7* `git tag v<VERSION> upstream/master && git push upstream --tags`
8
9After pushing, the release action will trigger. It will package it up, create a
10release on the GitHub release page, and trigger an update to the Bazel Central
11Registry (BCR).
12