Opened 2 years ago
Last modified 6 months ago
#60966 new task (blessed)
Introduce a GitHub Actions workflow for bumping the version number in a branch
| Reported by: | johnbillion | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Future Release |
| Component: | Build/Test Tools | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Focuses: |
Description
The process for bumping the version number of WordPress within a branch is highly manual and error prone. If a mistake is made or a test fails then it greatly slows down the release process for a branch while the automated test suites run again.
A GitHub Actions workflow should be introduced which:
- Accepts a WordPress version number input in
major.minorformat - Bumps the minor version number in all the required files in that branch (eg. from 6.5.0 to 6.5.1)
- Opens a PR with the changes so the tests can run
- Runs sanity checks to ensure that the about.php page already includes a changelog entry for that version, and fails the build if so
Files to update
- wp-includes/version.php
- package.json
- package-lock.json
Change History (4)
Note:
See TracTickets
for help on using tickets.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
I started on a proof of concept for this that can be seen at
A couple of observations/thoughts: