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: .github/ISSUE_TEMPLATE/4-REGULAR_RELEASE_CHECKLIST.md
+20-95Lines changed: 20 additions & 95 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -89,61 +89,27 @@ assignees: ''
89
89
composer require wp-cli/wp-cli:^2.1.0
90
90
```
91
91
92
-
### Updating the Phar build
92
+
### Updating the Phar build & Publishing GitHub Releases
93
93
94
94
- [ ] Create a PR from the `release-x-x-x` branch in `wp-cli/wp-cli-bundle` and merge it. This will trigger the `wp-cli-release.*` builds.
95
95
96
-
- [ ] Create a Git tag and push it. **Do not create a GitHub _release_ just yet**.
96
+
- [ ] Push the Git tag `v2.x.0` to [`wp-cli/wp-cli`](https://github.com/wp-cli/wp-cli/).
97
97
98
-
- [ ] Create a stable [Phar build](https://github.com/wp-cli/builds/tree/gh-pages/phar):
98
+
This automatically triggers the release workflow in `wp-cli/wp-cli` which:
99
+
- Generates the contributor list and changelog.
100
+
- Promotes the Phar and manifest in the `builds` repo to stable, generates checksums, and signs with GPG.
101
+
- Pushes the updated stable build back to `wp-cli/builds`.
102
+
- Creates draft releases with the changelog and all 7 attached assets on both [`wp-cli/wp-cli`](https://github.com/wp-cli/wp-cli/) and [`wp-cli/wp-cli-bundle`](https://github.com/wp-cli/wp-cli-bundle/).
Do this for both [`wp-cli/wp-cli`](https://github.com/wp-cli/wp-cli/) and [`wp-cli/wp-cli-bundle`](https://github.com/wp-cli/wp-cli-bundle/)
108
+
Publishing the release on `wp-cli/wp-cli` automatically triggers post-release automation workflows which:
109
+
- Bump the version to the next alpha in [`wp-cli/wp-cli`](https://github.com/wp-cli/wp-cli) (`VERSION` file and `composer.json` branch alias).
110
+
- Reset the framework dependency in [`wp-cli/wp-cli-bundle`](https://github.com/wp-cli/wp-cli-bundle) back to `"dev-main"`.
111
+
- Close the shipped milestones across all bundled repositories.
112
+
- Trigger handbook docs regeneration and website repository dispatch.
147
113
148
114
- [ ] Verify Phar release artifact
149
115
@@ -160,52 +126,11 @@ assignees: ''
160
126
<PHP serialized string with version numbers>
161
127
```
162
128
163
-
### Verify the Debian and RPM builds
164
-
165
-
- [ ] In the [`wp-cli/builds`](https://github.com/wp-cli/builds) repository, verify that the Debian and RPM builds exist
129
+
### Post-Release Manual Tasks
166
130
167
-
**Note:** Right now, they are actually already generated automatically before all the tagging happened.
131
+
- [ ] Update Homebrew formula (if not automated via action):
132
+
Follow this [example PR](https://github.com/Homebrew/homebrew-core/pull/152339) to update version numbers and sha256 for both `wp-cli` and `wp-cli-completion`.
168
133
169
-
- [ ] Change symlink of `deb/php-wpcli_latest_all.deb` to point to the new stable version.
170
-
171
-
### Updating the Homebrew formula (should happen automatically)
172
-
173
-
- [ ] Follow this [example PR](https://github.com/Homebrew/homebrew-core/pull/152339) to update version numbers and sha256 for both `wp-cli` and `wp-cli-completion`
174
-
175
-
### Updating the website
176
-
177
-
- [ ] Verify <https://github.com/wp-cli/wp-cli.github.com#readme> is up-to-date
178
-
179
-
- [ ] Update all version references on the homepage (and localized homepages).
180
-
181
-
Can be mostly done by using search and replace for the version number and the blog post URL.
182
-
183
-
- [ ] Update the [roadmap](https://make.wordpress.org/cli/handbook/roadmap/) to mention the current stable version
184
-
185
-
- [ ] Tag a release of the website
186
-
187
-
### Announcing
188
-
189
-
- [ ] Publish the blog post
190
-
191
-
- [ ] Announce release on the [WP-CLI Twitter account](https://twitter.com/wpcli)
192
-
193
-
- [ ] Optional: Announce using the `/announce` slash command in the [`#cli`](https://wordpress.slack.com/messages/C02RP4T41) Slack room.
194
-
195
-
This pings a lot of people, so it's not always desired. Plus, the blog post will pop up on Slack anyway.
196
-
197
-
### Bumping WP-CLI version again
198
-
199
-
- [ ] Bump [VERSION](https://github.com/wp-cli/wp-cli/blob/master/VERSION) in [`wp-cli/wp-cli`](https://github.com/wp-cli/wp-cli) again.
200
-
201
-
For instance, if the release version was `2.8.0`, the version should be bumped to `2.9.0-alpha`.
202
-
203
-
Doing so ensures `wp cli update --nightly` works as expected.
204
-
205
-
- [ ] Change the version constraint on `"wp-cli/wp-cli"` in `wp-cli/wp-cli-bundle`'s [`composer.json`](https://github.com/wp-cli/wp-cli-bundle/blob/master/composer.json) file back to `"dev-main"`.
206
-
207
-
```
208
-
composer require wp-cli/wp-cli:dev-main
209
-
```
134
+
- [ ] Publish the release blog post on the [make.wordpress.org CLI blog](https://make.wordpress.org/cli/).
210
135
211
-
- [ ] Adapt the branch alias in `wp-cli/wp-cli`'s [`composer.json`](https://github.com/wp-cli/wp-cli/blob/master/composer.json) file to match the new alpha version.
0 commit comments