Skip to content

Commit 40ada37

Browse files
authored
Merge pull request #3286 from Parsely/remove/outdated-github-release-issue-template
2 parents 35295cf + 4718600 commit 40ada37

File tree

2 files changed

+8
-77
lines changed

2 files changed

+8
-77
lines changed

.github/ISSUE_TEMPLATE/release-template-new.md

Lines changed: 0 additions & 68 deletions
This file was deleted.

.github/ISSUE_TEMPLATE/release-template.md

Lines changed: 8 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -33,21 +33,20 @@ The following additional tasks might be needed depending on the release and its
3333
## Release process
3434

3535
**1. Update version numbers and changelog**
36-
- [ ] Run `php bin/release.php $OLD_VERSION $NEW_VERSION` to update version numbers, the changelog, and to push the PR to GitHub. Copy the changelog's new release text for later use.
37-
- [ ] Verify that the PR code looks correct. You can amend it with new commits if needed.
36+
- [ ] [Run the "Bump wp-parsely version"](https://github.com/Parsely/wp-parsely/actions/workflows/bump-version.yml) GitHub Action to update the version numbers in the plugin files. Use the branch you want to release from (usually `develop`).
37+
- [ ] Verify that the generated PR looks correct. You can amend it with new commits if needed.
3838
- [ ] Merge the PR into the target branch (usually `develop`).
3939

4040
**2. Merge develop into trunk**
4141
- [ ] [Create a PR](https://github.com/Parsely/wp-parsely/compare/trunk...develop?quick_pull=1&title=Release+wp-parsely+x.y.z&body=This+PR+merges+the+`develop`+branch+into+the+`trunk`+branch+in+order+to+release+wp-parsely+x.y.z.) that merges the target branch (usually `develop`) into `trunk`, named _Release wp-parsely x.y.z_.
4242
- [ ] Merge the PR into `trunk`.
4343

44-
**3. Create the GitHub release**
45-
- [ ] [Create a GitHub release](https://github.com/Parsely/wp-parsely/releases/new?target=trunk) that targets `trunk`.
46-
- [ ] For the release's text, use the changelog text that was posted by the `bin/release.php` script into the PR in step 1.
47-
- [ ] Verify that you're using the appropriate name and tag (should be the version that is being released, without a leading 'v' character), and publish the release.
48-
49-
**4. Deploy the release to wordpress.org**
50-
- [ ] Run the [Deploy to WordPress.org](https://github.com/Parsely/wp-parsely/actions/workflows/deploy.yml) GitHub workflow, selecting the new version tag.
44+
**3. Create release and deploy to WordPress.org**
45+
- [ ] Check if the `develop` and `trunk` branches built successfully. You can check it in the [GitHub Actions](https://github.com/Parsely/wp-parsely/actions/workflows/build-plugin.yml) tab.
46+
- [ ] [Run the "Release wp-parsely"](https://github.com/Parsely/wp-parsely/actions/workflows/release-plugin.yml) GitHub Action, on the `trunk-built` branch, inputting the new version number, and without selecting Dry run.
47+
- [ ] Check the action logs for any errors. If there are any, fix them and rerun the action.
48+
- [ ] Check the new release on the [GitHub releases page](https://github.com/Parsely/wp-parsely/releases) and verify that it is correct.
49+
- [ ] Verify that the release was successful by checking the [WordPress.org plugin page](https://wordpress.org/plugins/wp-parsely/).
5150

5251
## After releasing
5352

0 commit comments

Comments
 (0)