@@ -10,13 +10,14 @@ Release checklist
1010 - [ ] Move anything that is still open in the current milestone to the new ` Next release ` milestone.
1111- [ ] Verify that any PR merged since the last release has a milestone attached to it.
1212- [ ] Create a changelog based on everything in the milestone, pull the changelog changes & merge the PR.
13- Verify that a release link at the bottom of the ` CHANGELOG.md ` file has been added.
13+ Verify that a release link at the bottom of the ` CHANGELOG.md ` file has been added.
1414- [ ] Double-check that nothing was merged into the ` main ` branch.
1515 - If there are unreleased commits in ` main ` , merge ` main ` into ` develop ` or cherrypick the commits from main into the ` develop ` branch.
1616
1717## Release
1818
1919- [ ] Open a PR to merge the ` develop ` branch to ` main ` .
20+ - Pro-tip: use this release checklist as the PR description to document that this release checklist has been followed.
2021- [ ] Merge that PR once all CI checks have passed.
2122- [ ] Create a release on GitHub, also creating a new tag (targeting ` main ` ) in the process, and copy & paste the changelog to it.
2223 - Add/edit the relevant links to the bottom of the changelog to make sure all texts between ` [] ` in changelog entries become links.
@@ -27,8 +28,8 @@ Release checklist
2728
2829## Announce
2930
30- - [ ] Add a message to the ` #yoastcs ` Slack channel on the [ Yoast Slack] ( https://yoast.slack.com/ ) to announce the new release:
31- ```
32- We just released YoastCS x.y.z
33- Changelog: https://github.com/Yoast/yoastcs/releases/tag/x.y.z
34- ```
31+ - [ ] Post a message in the ` #yoastcs ` Slack channel on the [ Yoast Slack] ( https://yoast.slack.com/ ) to announce the new release:
32+ ```
33+ We just released YoastCS x.y.z
34+ Changelog: https://github.com/Yoast/yoastcs/releases/tag/x.y.z
35+ ```
0 commit comments