-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
17 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
--- | ||
name: Release Checklist | ||
about: A checklist of tasks required to make a release | ||
title: release <updated-microservice>-MAJOR.MINOR.PATCH | ||
labels: '' | ||
assignees: '' | ||
|
||
--- | ||
|
||
- [ ] Create a branch for the release | ||
- [ ] Update the dependencies using pip-compile (do not use dependabot) | ||
- [ ] Update the GHCR image tag in `compose.prod.yml` to the imminent release version | ||
- [ ] Bump the `"version"` number in `__init.py__` or relevant file | ||
- [ ] Update the base image version in the Dockerfile if necessary (this should be the most recent LTS version) and do a test build and run of the Docker image on your local machine so you know if something is going to go off the rails before the automated build action on GitHub. | ||
- [ ] Open a PR that merges the release branch into main. | ||
- [ ] Merge the release PR after it passes testing and review. | ||
- [ ] Tag a corresponding release on GitHub. This will trigger an automated Docker image build on GitHub. If the build succeeds it will be automatically published to GHCR. See [wiki](https://github.com/legumeinfo/microservices/wiki/Tagging-Releases-and-Automated-Builds) for details on tagging |