diff --git a/.github/ISSUE_TEMPLATE/dev_release_minor_version.md b/.github/ISSUE_TEMPLATE/dev_release_minor_version.md index fbee276ec..b559b850a 100644 --- a/.github/ISSUE_TEMPLATE/dev_release_minor_version.md +++ b/.github/ISSUE_TEMPLATE/dev_release_minor_version.md @@ -24,7 +24,7 @@ On the release branch: - [ ] Wait for GitHub Actions to complete and no failed jobs. - [ ] Publish new RC releases (e.g. `v0.12.0-rc.1`, `v0.12.0-rc.2`) to ensure Docker workflow succeeds. **Make sure the tag is created on the release branch**. - [ ] Pull down the Docker image and [run through application setup](https://github.com/gogs/gogs/blob/main/docker/README.md) to make sure nothing blows up. -- [ ] - [ ] Publish a new [GitHub release](https://github.com/gogs/gogs/releases) with entries from [CHANGELOG](https://github.com/gogs/gogs/blob/main/CHANGELOG.md) for the current minor release. **Make sure the tag is created on the release branch**. +- [ ] Publish a new [GitHub release](https://github.com/gogs/gogs/releases) with entries from [CHANGELOG](https://github.com/gogs/gogs/blob/main/CHANGELOG.md) for the current minor release. **Make sure the tag is created on the release branch**. - [ ] Only mention patch authors for the current release. - [ ] [Wait for a new image tag for the current release](https://github.com/gogs/gogs/actions/workflows/docker.yml?query=event%3Arelease) to be created automatically on both [Docker Hub](https://hub.docker.com/r/gogs/gogs/tags) and [GitHub Container registry](https://github.com/gogs/gogs/pkgs/container/gogs). - [ ] [Push a new Docker image tag](https://github.com/gogs/gogs/blob/main/docs/dev/release/release_new_version.md#update-docker-image-tag) as `.` to both [Docker Hub](https://hub.docker.com/r/gogs/gogs/tags) and [GitHub Container registry](https://github.com/gogs/gogs/pkgs/container/gogs), e.g.: diff --git a/.github/ISSUE_TEMPLATE/dev_release_patch_version.md b/.github/ISSUE_TEMPLATE/dev_release_patch_version.md index 05658c519..6101661cb 100644 --- a/.github/ISSUE_TEMPLATE/dev_release_patch_version.md +++ b/.github/ISSUE_TEMPLATE/dev_release_patch_version.md @@ -12,8 +12,6 @@ _This is generated from the [patch release template](https://github.com/gogs/gog On the release branch: - [ ] Make sure all commits are cherry-picked from the `main` branch by checking the patch milestone. -- [ ] Run `git log v0.12.1...HEAD --pretty=format:'- %H %s' --reverse` (where `v0.12.1` is the last patch release) to get the list of new commits and paste the output below: - - _link to the commit_ - [ ] [Update CHANGELOG on the `main` branch](https://github.com/gogs/gogs/commit/e6c5633f580399c8f4dfc07166a63a01c6c70346) to include entries for the current patch release. ## During release @@ -53,6 +51,6 @@ On the `main` branch: The .. has been released that includes the patch of the reported issue. ``` - [ ] Update the repository mirror on [Gitee](https://gitee.com/unknwon/gogs). -- [ ] Reply to the release topic for the minor release in [Discussions](https://github.com/gogs/gogs/discussions/categories/announcements). +- [ ] Create a new release announcement in [Discussions](https://github.com/gogs/gogs/discussions/categories/announcements). - [ ] Send a tweet on the [official Twitter account](https://twitter.com/GogsHQ) for the patch release. - [ ] Close the patch milestone.