Use the below text for a release PR to merge develop into master and adjust the placeholders between [square brackets] to the correct information for that release:
PR for tracking changes for the [x.x.x] release. Target release date: [Weekday Month Day Year].
- Check the wiki against vandalism.
- Verify, and if necessary, update the allowed version ranges for various dependencies in the
composer.json- PR #[#] - [Major releases only] Update the aliases in
extra -> branch-aliasin thecomposer.jsonfile - [Major releases only] Update the
COMPOSER_ROOT_VERSIONin the GH Actions files - Add changelog for the release - PR #[#] :pencil2: Remember to create a link to the milestone and to the diff at the bottom of the file.
- Merge this PR
- Make sure all CI builds are green.
- Add release tag against
master(careful, GH defaults todevelop!) & copy & paste the changelog to it :pencil2: Make sure to copy the relevant links from the bottom of the changelog as well. - Close the milestone for the release
- Open a new milestone for the next release
- If any open PRs which were milestoned for this release do not make it into the release, update their milestone.
- Fast-forward
developto be equal tomaster
- Post on Mastodon about the release.
- Tweet about the release.
- Post about it in Slack. (WordPress #tide channel and any others people deem relevant)