Review nightly builds usage and workflow
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start with the WordPress Handbook section linked in the issue and compare the existing Beta/RC and bleeding-edge nightly publishing paths across Roots' packages. Investigate how point-release nightlies could follow the documented branch-development API and determine what automation is needed for 6.2.x-style branches; done means point release nightlies are published and consumable consistently.
Written by the indexing model from the issue text.
Description
As described in the WordPress Handbook, three different nightly builds are available:
- Point release nightlies. The current release is 6.2.2. Selecting this will put you on the track for 6.2.x development.
(e.g.,https://wordpress.org/nightly-builds/wordpress-6.2-latest.zip, API call)- Bleeding edge nightlies. Selecting this will put you on the track for 6.3 development.
(e.g.,https://wordpress.org/nightly-builds/wordpress-latest.zip, API call)- Beta/RC. Selecting this will update to the next released beta or RC on whichever branch you are currently running.
(e.g.,https://downloads.wordpress.org/release/wordpress-6.3-rc2.zip)
Currently, the following has been implemented and is available across Roots' packages:
- Beta/RC. 👌 Well tagged and correctly published. Nothing to do.
- With the known limitation for the
no-contentedition as per https://github.com/roots/wordpress-no-content/issues/4
- With the known limitation for the
- Bleeding edge nightlies. 🙂 Published on
mainbranches.- Their constraints (like PHP version) might be suitable to automation, but all good so far.
- Point release nightlies. ☹️ Not handled yet.
- Could be done via
6.2-dev-ish tags (not allowed)6.2.x-ish branches but requires automation.
- Could be done via
- Dominant language
- PHP
- Stars
- 43
- Forks
- 8
- Avg merge
- 1m
- Merged PRs (30d)
- 10
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from roots/wordpress-packager
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 52/100
roots/wordpress-packager#1296 · 6 comments · 3 reactions ·
Maintainers usually reply within 1 day
All issues in roots/wordpress-packager
Similar issues
-
Difficulty 2/5 Half a day Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
sonata-project/dev-kit#3119 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
🧠 Admin
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
RSA PKCS#1 v1.5 verify fails for SHA-512/224, SHA-512/256 and SHA-3 (UnhandledMatchError on 4.x)Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day