Skip to content

fix(platform): update GrowthBook to security release 5.2.1 - #675

Draft
wax911 wants to merge 1 commit into
devfrom
fix/growthbook-5-2-1-security
Draft

wax911 wants to merge 1 commit into
devfrom
fix/growthbook-5-2-1-security

Conversation

@wax911

@wax911 wax911 commented Nov 18, 2026

Copy link
Copy Markdown
Member

Summary

Propose the official GrowthBook 5.2.1 security release in place of 5.1.0. Only the owning dashboard Compose image and reproducibly regenerated platform stack change; volumes, routes, limits, healthcheck and entrypoint are unchanged.

The published 5.1.0 ARM64 image sha256:c8a124f55dca3b2e2ecc3f316c28e5cbe960f1e2988541e3ce30a5b3ed7ab003 contains Next.js 16.3.5, covered by critical GHSA-2464-fhr4-w9xw. Its inventory also flags certifi and other critical dependency findings. The 5.2.1 source declares Next.js ~16.4.5 and other security updates, but registry access became Forbidden before the candidate image could be inspected. This is partial remediation work, not a claim that the candidate or production is clean.

Verification

  • Used the repository's SHA-256-pinned stackctl 0.4.0 generator. Repeated generation has identical YAML semantics, with exactly the expected image change.
  • All 29 generator/render tests, yamllint, shell syntax, diff checks and the repository-style filesystem vulnerability scan passed locally.
  • Ran ./stackctl.sh sync --quiet on base and candidate: both exit 1 for pre-existing byte-format drift. Native CI semantic drift validation remains required.
  • Ran ./stackctl.sh up --dry-run --no-logs on base and candidate: both exit 2 because this environment lacks Docker. No validation substitute or deployment was used.

Before promotion

Keep as draft pending independent review. Require full candidate image scans for supported architectures, exact-head native stack CI, and staging checks of dashboard/API, feature delivery, tracing and the unchanged Node healthcheck. Review 5.2 behavior, MongoDB/uploads backup, state compatibility and the rollback plan. Do not assume a minor version is nonbreaking. No auto-merge, release or deployment is requested.

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