aboutsummaryrefslogtreecommitdiff
path: root/RELEASING.md
blob: 72059f23d11e60c2fe347af502ba6f95e8316ca3 (plain)
1
2
3
4
5
6
7
8
9
10
11
# Releases

Releases are mostly automated and triggered by adding a tag:

Assuming you have a remote named `upstream` pointing to the repo:

* `git tag v<VERSION> upstream/master && git push upstream --tags`

After pushing, the release action will trigger. It will package it up, create a
release on the GitHub release page, and trigger an update to the Bazel Central
Registry (BCR).