aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authortechknowlogick <techknowlogick@gitea.io>2022-03-03 15:59:26 -0500
committerGitHub <noreply@github.com>2022-03-03 15:59:26 -0500
commit286355c7548b273f73f69cb79d8eaff8e05a8622 (patch)
tree874122e3cfa25543ef6316978b3bfa6d581d12a5
parent7a893dab396c24d7e158b190f0a0182ff75bbcfd (diff)
downloadgitea-286355c7548b273f73f69cb79d8eaff8e05a8622.tar.gz
gitea-286355c7548b273f73f69cb79d8eaff8e05a8622.zip
homebrew updates via cron
-rw-r--r--CONTRIBUTING.md1
1 files changed, 0 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 4216ee3a13..45344a4d7b 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -424,7 +424,6 @@ be reviewed by two maintainers and must pass the automatic tests.
* If needed send a frontport PR for the changelog to branch `main` and update the version in `docs/config.yaml` to refer to the new version.
* Send PR to [blog repository](https://gitea.com/gitea/blog) announcing the release.
* Verify all release assets were correctly published through CI on dl.gitea.io and GitHub releases. Once ACKed:
- * send a PR to the [homebrew repo](https://gitea.com/gitea/homebrew-gitea) analog to [this PR](https://gitea.com/gitea/homebrew-gitea/commit/1f9a3fe5eb75b64a96a5336665531abcbd0eef0c)
* bump the version of https://dl.gitea.io/gitea/version.json
* merge the blog post PR
* announce the release in discord `#announcements`