Skip to content

chore(release): prepare v4.14.1 - #1967

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

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

Conversation

@mrrobot47

@mrrobot47 mrrobot47 commented Nov 19, 2026 •

Copy link
Copy Markdown
Member

Summary

Refs #1966

Upgrade notes

  • ee cli update pulls the new nginx-proxy image and recreates only the global proxy. Sites are unreachable for the few seconds the proxy takes to restart; site containers aren't touched.
  • The update checks the running proxy's configuration with nginx -t first and stops without changing anything if it fails. If the new proxy doesn't come up, the previous one is restored.
  • The per-site nginx image (OpenResty 1.31.8.1) is unchanged: it serves plain HTTP/1.1 to the proxy only, without HTTP/2 or TLS. It will be updated once OpenResty 1.31.9.1 is released.

Testing

  • easyengine/nginx-proxy:v4.14.1 as published: nginx -v is 1.31.9, nginx -t passes with our config and with all dynamic modules loaded, docker-gen renders the template for a test site, and over HTTPS ALPN negotiates h2 and both HTTP/2 and HTTP/1.1 requests are proxied to the backend.
  • Upgrade from stable 4.14.0 to a phar built from this branch, with a WordPress, a PHP and a self-signed HTTPS site: the update exits 0; only the global proxy is recreated (all site containers and the global db keep running with the same IDs); the proxy reports nginx 1.31.9 and EasyEngine v4.14.1; the sites return the same responses before and after, including HTTP/2 over HTTPS; no new migration rows. Sites were unreachable for about 1 s or less while the proxy was swapped (0.3 s on a GitHub runner, 0.5–1.1 s on a test server). As on every update, the global cron container is restarted when its config is regenerated.

Move easyengine/nginx-proxy to v4.14.1, which updates its nginx from 1.31.3 to 1.31.9 for the nginx security fixes of 2026-11-18 (CVE-2026-123633, CVE-2026-123007, CVE-2026-118899, CVE-2026-123634) and the earlier 1.31.6 and 1.31.7 fixes (EasyEngine/dockerfiles#379). The other images are unchanged.
@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 update

Layer / File(s) Summary
Update release version values
VERSION, img-versions.json
VERSION changes to 4.14.1. The easyengine/nginx-proxy image tag changes to v4.14.1.

Possibly related issues

Possibly related PRs

Change: Other

Merge Risk: Minimal · up to f35ad

This release bump moves the CLI version and the proxy image tag to 4.14.1 to pick up the nginx security fixes. No code defects were identified, so the change looks ready to merge once the author finishes the planned smoke and upgrade tests.

Security architecture risk: Minimal · up to f35ad

The inspected change updates the release identifier and proxy image without changing deployment logic or adding permissions. Existing checks and recovery handling remain in place. No introduced or worsened architecture risk was established; the published image contents and actual deployment privileges were not independently verified.

Retained concerns
No architecture-level concerns identified.

Security review details

Security Blast Radius

  • inferred — The changed executable image belongs to the shared global proxy rather than a per-site container. A failed proxy replacement can therefore interrupt sites relying on that proxy within an affected installation. Exact tenant, host and data exposure cannot be bounded without the deployed service definition and image contents.

Trust Boundaries and Controls

  • observed — The repository selects the replacement image using a registry name and version tag, preserving the pre-existing reliance on the registry's tag-to-content binding. The change neither adds a digest binding nor demonstrates compromised image content or expanded deployment authority.

Resilience and Maintainability Implications

  • observed — The running-proxy precheck rejects configuration-test failure or timeout before replacement, and image-version persistence follows migration execution steps. These existing controls support failure containment, but readiness probes do not independently establish HTTPS, HTTP/2 or vulnerability-remediation correctness.
Finishing Touches

Generate unit tests (beta)

  • 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: 7461c56e-cc65-4913-9a6f-bbc98361748d
Commits

Reviewing files that changed from the base of the PR and between 090c5c0 and f35adb1.

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; 9 remain after this review.

@mrrobot47
mrrobot47 merged commit 512b43e into EasyEngine:develop Nov 19, 2026
33 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