Skip to content

Commit bcffd4a

Browse files
committed
Release checklist: minor textual tweak after feedback [2]
1 parent d3f6a69 commit bcffd4a

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

.github/release-checklist.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -93,9 +93,9 @@ Please consider [funding the PHP_CodeSniffer project](https://opencollective.com
9393
certutil -hashfile ./phpcbf-x.x.x.phar SHA256
9494
```
9595
- Update the `gh-pages` branch:
96-
- [ ] Add the new release to the `phive.xml` file,
97-
- [ ] Add the versioned PHAR files + keys in PHAR dir
98-
- [ ] Add the unversioned PHAR files + keys in root dir
96+
- [ ] Add the new release to the `phive.xml` file.
97+
- [ ] Add the versioned PHAR files + keys in PHAR dir.
98+
- [ ] Add the unversioned PHAR files + keys in root dir.
9999
- [ ] Verify the attestations of the PHAR files.
100100
```bash
101101
gh attestation verify phpcs.phar -o PHPCSStandards
@@ -106,14 +106,14 @@ Please consider [funding the PHP_CodeSniffer project](https://opencollective.com
106106
- [ ] Commit & push the changes.
107107
- [ ] Verify that the website regenerated correctly and that the phars can be downloaded.
108108
- [ ] Create a release & copy & paste the changelog to it.
109-
- [ ] Upload the unversioned PHAR files + asc files to the release
110-
- [ ] Announce the release in the discussions forum via checkbox
109+
- [ ] Upload the unversioned PHAR files + asc files to the release.
110+
- [ ] Announce the release in the discussions forum by checking the checkbox at the bottom of the release page.
111111
- [ ] Make sure all CI builds are green, including the verify-release workflow.
112112

113113

114114
## After Release
115115

116-
- [ ] Update the version nr in `Config::VERSION` file to the _next_ (patch) version.
116+
- [ ] Update the version number in the `Config::VERSION` class constant in the `src/Config.php` file to the _next_ (patch) version.
117117
This can always be adjusted again later if needs be if it is decided that the next version will be a minor/major, but at least for dev
118118
it should clearly show that this is bleeding edge/unreleased.
119119
- [ ] Close release announcement in the "Discussions" for previous minors (leave the announcements related to the current minor open).

0 commit comments

Comments
 (0)