Repository navigation
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
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. |
b5a3aa5 to
ec466db
Compare
|
Size Change: 0 B Total Size: 1.33 MB ℹ️ View Unchanged
|
ec466db to
a4849fa
Compare
|
Size Change: 0 B Total Size: 1.33 MB ℹ️ View Unchanged
|
Part of #82931.
What?
Pins the MariaDB version
wp-envuses on this branch to10.11, by setting"mariadbVersion": "10.11"in.wp-env.json.Why?
Without a pin,
wp-envruns the floatingmariadbimage: whatever the newest MariaDB release is at the time, many years newer than anything WordPress 6.2 was released against.10.11is the latest MariaDB LTS release that came out before WordPress 6.2, so the database now matches that release's era.How?
Uses the
mariadbVersionoption added in #84232. The value applies to both the development and tests environments. #84235, the PR below this one, makeswp-env startwork with MariaDB releases before 11.4, so the10.11pin starts cleanly.Checked with this branch's own
wp-envcode:readConfig()returnsmariadbVersion10.11for both environments, and the generated Docker Compose configuration usesmariadb:10.11for both themysqlandtests-mysqlservices.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.