Skip to content

chore(release): prepare v4.14.2 - #1970

Merged
mrrobot47 merged 2 commits into
EasyEngine:developfrom
mrrobot47:release/v4.14.2
Nov 19, 2026
Merged

mrrobot47 merged 2 commits into
EasyEngine:developfrom
mrrobot47:release/v4.14.2

Conversation

@mrrobot47

@mrrobot47 mrrobot47 commented Nov 19, 2026 •

Copy link
Copy Markdown
Member

Summary

Upgrade notes

  • ee cli update moves every enabled site on PHP 8.2–8.5 to the patched image: each such site is recreated one at a time, with temporary support containers serving it meanwhile. Disabled sites get updated compose files and start on the patched image when enabled.
  • PHP 8.1 and older are end of life and get no fixes; sites on them are untouched.

Testing

  • Images (easyengine/php8.2–php8.5:v4.14.2): PHP 8.2.36, 8.3.37, 8.4.28 and 8.5.13; CLI and FPM modules, conf.d and extension files identical to v4.14.0, no extension load warnings; WP-CLI and Composer present.
  • Upgrade to a phar built from this branch, from stable 4.14.1 and from stable 4.14.0, with WordPress sites on PHP 8.2–8.5 (one with Redis cache), a PHP site, a local-database site, an HTML site, a PHP 8.1 site and a disabled site: the update exits 0; only the sites on PHP 8.2–8.5 are recreated, on the new images, one at a time; HTML and PHP 8.1 sites and the global database and Redis aren't touched; the proxy stays on v4.14.1 (from 4.14.0 it's recreated once for v4.14.1's nginx, ready after about 2 s with the new 180 s default wait). Every site returns 200 before and after; the Redis object and page cache, PHP sessions and the local database keep working; the disabled site's compose file moves to the new image and ee site enable starts it on it. Sites were unreachable for at most a few seconds at each container switch (under 5 s on a test server, under 0.5 s on a GitHub runner).
  • After the update: new sites on 8.2–8.5 and --php=latest get the new images (a new 8.2 site with --cache has a working Redis object cache), and ee site update --php=8.5 moves a site to the new 8.5 image.
  • Behat CI on this PR: green on PHP 7.4–8.5.

@coderabbitai

coderabbitai Bot commented Nov 19, 2026 •

Copy link
Copy Markdown

Explain Change →

No actionable comments were generated in the recent review.

Walkthrough

Changes: Release version updates

Layer / File(s) Summary
Align release and PHP image versions
VERSION, img-versions.json
The release version changed from 4.14.1 to 4.14.2. The listed PHP 8.2–8.5 image versions changed from v4.14.0 to v4.14.2.

Change: Other

Merge Risk: Low · up to 5a0fb

This release only updates the version number and the PHP 8.2–8.5 image tags to v4.14.2. It should not merge or ship until all four v4.14.2 images are published, otherwise site creation and recreation on those PHP versions would fail to pull the image. The code change itself is small and consistent.

Security architecture risk: Minimal · up to 5a0fb

The release changes four PHP image tags without changing image publishers, permissions or update logic. No introduced or worsened security or failure-containment issue was established. Image publication and the claimed upstream fixes remain unverified.

Retained concerns
No architecture-level concerns identified.

Security review details

Security Blast Radius

  • inferred — Within each installation adopting this release, the changed bindings can affect enabled sites selected through the four PHP image families and disabled sites whose compose tags are stale. The updater iterates all site records, so the rollout scope is not limited to a single site.

Trust Boundaries and Controls

  • observed — Runtime tag selection continues to originate from the release manifest under EE_ROOT and the same EasyEngine image repositories. The repository delta introduces no new registry selector, identity, credential or permission configuration; the external images' effective contents and privileges were not inspected.

Resilience and Maintainability Implications

  • observed — The unchanged migration processor captures step failures before proceeding to version recording and attempts cleanup through registered recovery steps. This supports failure containment for caught errors, but does not establish crash-safe or concurrent-update guarantees.
Finishing Touches

Generate unit tests (beta)

  • Create a new PR
Fix failing CI checks

  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Recent review info

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Repository UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: e1466d62-bb89-475c-8961-4b8bba695b94
Commits

Reviewing files that changed from the base of the PR and between b57912f and 5a0fb09.

Files selected for processing: 2

  • VERSION
  • img-versions.json

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 6 remain after this review.

@mrrobot47
mrrobot47 merged commit c013f06 into EasyEngine:develop Nov 19, 2026
36 of 64 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant