Automated patch release: 2.10.5

[github-actions]

Changes in this pull request

• Bumped version from 2.10.4 to 2.10.5
• ℹ️ Notice: post-set-version script not defined.
• ✅ Ran npm script: build
• ✅ Ran composer script: i18n

Merged PRs since last release

• NPM(deps): Bump @wordpress/api-fetch from 7.52.0 to 7.53.0 #573 NPM(deps): Bump @wordpress/api-fetch from 7.52.0 to 7.53.0
• NPM Dev(deps-dev): Bump @wordpress/url from 4.52.0 to 4.53.0 #572 NPM Dev(deps-dev): Bump @wordpress/url from 4.52.0 to 4.53.0
• NPM Dev(deps-dev): Bump @wordpress/dom-ready from 4.52.0 to 4.53.0 #571 NPM Dev(deps-dev): Bump @wordpress/dom-ready from 4.52.0 to 4.53.0
• Composer Dev(deps-dev): Bump johnpbloch/wordpress from 7.0.3 to 7.0.4 #568 Composer Dev(deps-dev): Bump johnpbloch/wordpress from 7.0.3 to 7.0.4
• NPM(deps): Bump react-svg from 19.1.3 to 19.1.4 #567 NPM(deps): Bump react-svg from 19.1.3 to 19.1.4
• Composer(deps): Bump newfold-labs/wp-module-data from 2.9.6 to 2.9.7 #566 Composer(deps): Bump newfold-labs/wp-module-data from 2.9.6 to 2.9.7
• Resolve Dependabot security alerts #565 Resolve Dependabot security alerts
• Automated patch release: 2.10.4 #564 Automated patch release: 2.10.4
• Use clear installer queue helper #563 Use clear installer queue helper
• NPM(deps): Bump react-svg from 19.1.1 to 19.1.3 #561 NPM(deps): Bump react-svg from 19.1.1 to 19.1.3

Generated automatically by CI workflow (see prep-release workflow).

[github-actions]

AI code review

✅ Strengths

• Version bump to 2.10.5 is applied consistently in package.json and package-lock.json.
• i18n artifacts regenerated across all locales with updated revision timestamps; build and composer i18n steps were executed as noted.
• No functional code changes in this patch release, keeping risk low and scope tight for a quick ship.

⚠️ Suggestions (non-blocking)

• Consider adding a post-set-version script (or muting the workflow step) to avoid the recurring “post-set-version script not defined” notice in release PRs.
• Please update docs/changelog.md for 2.10.5 per repo guidance, and confirm any release notes/tagging steps in the workflow are in place.
• Align toolchain versions if practical: JSON files show generator: WP-CLI/2.12.0 while .l10n.php files list WP-CLI 2.11.0. Not blocking, but consistent tooling helps reproducibility.
• Double-check versioning outside npm (e.g., any PHP header/constants or plugin loader registration that might also carry a version) to ensure the release number is reflected everywhere the project surfaces it.
• Sanity-check JS text domains: the JSON uses domain: "messages" while some .po files carry X-Domain: wp-module-solutions. If intentional, ignore; if not, ensure wp_set_script_translations and extraction domains match to avoid missing translations.

❌ Issues (blocking)

• None detected. No code or dependency changes in this diff that would pose stability, security, or performance risk.

Verdict

⚠️ Verdict: Low-risk automated patch release. Recommend merge with minor follow-ups (changelog update, optional workflow/tooling alignment).

[github-actions]

Coverage: Base 45.42% → PR 45.42% (must not decrease).
✅ No decrease.

project coverage report 45.42% @ d0af5e9