Skip to content

Commit 133731d

Browse files
authored
Updated how to release docs (#625)
1 parent 4cbc17a commit 133731d

File tree

2 files changed

+9
-47
lines changed

2 files changed

+9
-47
lines changed

.github/workflows/create-release-pr.yml

-36
This file was deleted.

docs/how-to-release.md

+9-11
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,15 @@
11

22
## How to Release
33

4-
* Ensure the versions specified in [release.json](../release.json) are correct.
5-
* Prepare a PR to bump and versions as required.
6-
7-
* Ensure that [the release notes](./RELEASE_NOTES.md) are up to date for this release.
8-
* Review the [tickets for this release](https://jira.mongodb.org/issues?jql=project%20%3D%20CLOUDP%20AND%20component%20%20%3D%20"Kubernetes%20Community"%20%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%20kube-community-0.6.0%20) (ensure relevant fix version is in the jql query)
9-
10-
* Run the `Create Release PR` GitHub Action
11-
* In the GitHub UI:
12-
* `Actions` > `Create Release PR` > `Run Workflow` (on master)
13-
14-
* Review and Approve the release PR that is created by this action.
4+
* Prepare release PR:
5+
* Update any changing versions in [release.json](../release.json).
6+
* Ensure that [the release notes](./RELEASE_NOTES.md) are up to date for this release.
7+
* Run `python scripts/ci/update_release.py` to update the relevant yaml manifests.
8+
* Commit all changes.
9+
* Create a PR with the title `Release MongoDB Kubernetes Operator v<operator-version>` (the title must match this pattern)
10+
11+
* Have this PR Reviewed and Approved.
1512
* Upon approval, all new images for this release will be built and released, and a Github release draft will be created.
13+
* No need to merge this PR, when all images are successfully released, the PR will be merged.
1614

1715
* Review and publish the new GitHub release draft.

0 commit comments

Comments
 (0)