Repository navigation
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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:c8a124f55dca3b2e2ecc3f316c28e5cbe960f1e2988541e3ce30a5b3ed7ab003contains 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
./stackctl.sh sync --quieton base and candidate: both exit 1 for pre-existing byte-format drift. Native CI semantic drift validation remains required../stackctl.sh up --dry-run --no-logson 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.