You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/RELEASING.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,6 @@ Steps to publish a new Karate release. Replace `X.Y.Z` with the version being re
4
4
5
5
## 1. Prepare the Release
6
6
7
-
-[ ] Manually close or defer each open issue on the `X.Y.Z` milestone via the GitHub UI (issues labeled `fixed` typically just need to be closed)
8
7
-[ ] Verify `main` is green on CI
9
8
-[ ] Update version in `pom.xml` (remove any `-SNAPSHOT` or `.RC*` suffix):
10
9
```bash
@@ -35,10 +34,11 @@ Steps to publish a new Karate release. Replace `X.Y.Z` with the version being re
35
34
-`cve-sbom-report.html`
36
35
-[ ] See [v2.0.1](https://github.com/karatelabs/karate/releases/tag/v2.0.1) for reference
37
36
38
-
## 4. Close Milestone
37
+
## 4. Close Issues and Milestone
39
38
40
-
-[ ] Close the GitHub milestone for `X.Y.Z`
39
+
-[ ] Close each fixed issue on the `X.Y.Z` milestone via the GitHub UI, leaving a comment `vX.Y.Z released` on each (issues labeled `fixed` typically just need to be closed)
41
40
-[ ] Move any remaining open issues to the next milestone
0 commit comments