@@ -23,33 +23,15 @@ about: Steps to work through in order to publish a new release
23
23
- [ ] Create "Added", "Removed", "Changed" and "Fixed" sections, as
24
24
necessary.
25
25
- [ ] If relevant, add links to the corresponding PRs to the entries.
26
- - [ ] Set the revision in [ the ` start ` script] [ start ] and
27
- [ ` docs/haskell-use-cases ` ] [ usecases ] to the current release
28
- preparation branch; comment out the checksum. (n.b., Search for
29
- ` http_archive ` in these files.)
30
26
- [ ] Update the version of the modules in ` MODULE.bazel ` files
31
- - [ ] Push the ` release-<major>.<minor> ` branch and open a ** draft** PR
32
- to verify CI is green.
33
- - [ ] Create a release tag (` v<major>.<minor> ` ) on the release
34
- preparation branch and push the tag; or use Github's UI.
35
- - [ ] Go to the [ release page] [ releases ] :
36
- - [ ] Open the corresponding draft release and copy the workspace snippet.
37
- - [ ] Insert the workspace snippet into [ the ` start ` script] [ start ]
38
- and [ ` docs/haskell-use-cases ` ] [ usecases ] replacing the existing snippet.
39
- - [ ] Push the changes to the remote branch and mark the PR as ready;
40
- go through review and merge to ` master ` upon success.
41
- - If any changes need to be made, upon review, you will need to delete
42
- the release tag (from local and origin) and repeat the previous four
43
- steps appropriately before requesting a follow-up review.
44
- - If there are changes on the release preparation branch that should
45
- * not* go to ` master ` , create a second branch
46
- ` release-<major>.<minor>-master ` on ` master ` and cherry-pick all
47
- relevant commits from the release branch preparation branch. Open a
48
- pull request with that branch, go through review and push changes
49
- back to the release preparation branch.
50
- - [ ] Go to the [ release page] [ releases ] :
51
- - [ ] Open the draft release for the current version.
52
- - [ ] Release.
27
+ - [ ] Push the ` release-<major>.<minor> ` branch and open a PR; go through review and merge upon success.
28
+ - [ ] Trigger the ` Prepare Release ` workflow
29
+ - either via the Github UI ** or**
30
+ - run ` gh workflow run -f version=<major>.<minor> 'Prepare Release' ` using the Github CLI
31
+ - [ ] Go to the [ releases] , open the draft release which was created to inspect it
32
+ - Do the code snippets look valid?
33
+ - Is there a release artifact attached to it?
34
+ - If you're happy, publish the release... :rocket :
53
35
- [ ] After the "Publish" workflow is finished check whether https://haskell.build/start
54
36
is now the latest [ ` start ` script] [ start ] (Netlify sometimes has problems).
55
37
- [ ] Announce the new version on Twitter by asking someone with access.
0 commit comments