Conversation
a60b654 to
5b1e679
Compare
5b1e679 to
d3376ee
Compare
d3376ee to
d1aa805
Compare
d1aa805 to
e4ba88f
Compare
|
Flaky tests detected in 324a3d7. 🔍 Workflow run URL: https://github.com/desrosj/gutenberg/actions/runs/34634343874 should undo typing after non input change in
|
e4ba88f to
18d3739
Compare
18d3739 to
7a3213d
Compare
186830e to
a884c86
Compare
a884c86 to
5bfd1ec
Compare
5bfd1ec to
5159935
Compare
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
5159935 to
4908534
Compare
Pins wp-env's WordPress core checkout to `WordPress/WordPress#7.0-branch` via both `.wp-env.json`'s and `.wp-env.test.json`'s `"core"` value, and removes the `wordpress` test matrix dimension, the `WP_ENV_CORE` environment variable override, and the `compute-previous-wordpress-version` job it depended on from `unit-test.yml`'s `test-php` job. Both `.wp-env.json` and `.wp-env.test.json`'s `"core"` values were previously unpinned (`"WordPress/WordPress"`), so every PHP unit test run built against whatever commit happened to be on WordPress Core's own `trunk` at run time. That makes results non-reproducible and ties this frozen branch's CI to changes on a codebase it has no relationship to. Pinning both files to Core's own `7.0-branch` tests against a WordPress version this Gutenberg branch is actually meant to run alongside. `.wp-env.test.json` was missed in the original version of this commit — this branch is the first to carry that file, and its own `"core"` pin was overlooked alongside `.wp-env.json`'s.
4908534 to
324a3d7
Compare
|
Migrated to real upstream: WordPress#82802. Closing this fork PR. |
What?
Pins
wp-env's WordPress core checkout toWordPress/WordPress#7.0-branchvia.wp-env.json's"core"value, and removes thewordpresstest matrix dimension, theWP_ENV_COREenvironment variable override, and thecompute-previous-wordpress-versionjob it depended on fromunit-test.yml'stest-phpjob.Why?
.wp-env.json's"core"value was unpinned ("WordPress/WordPress"), so every PHP unit test run built its WordPress environment against whatever commit happened to be on WordPress Core's owntrunkat run time. That makestest-phpnon-reproducible and ties this frozen branch's CI to unrelated, ongoing changes on a different project's default branch — the opposite of what a maintenance branch's CI should depend on. Pinning to Core's own7.0-branchtests against the WordPress version this Gutenberg branch is actually meant to run alongside, and removing the "previous major version" matrix leg (along with the job that computed which version that was) drops a comparison that only made sense while tracking Core's movingtrunk.Use of AI Tools
This PR was created by Claude Code under my supervision. All code should be treated as AI-produced and not yet reviewed by a human until this PR is marked Ready for Review.