fix(plane-enterprise): bump iframely v1.2.0 -> v2.5.4 - #312
Conversation
The chart's iframely default was still v1.2.0 (Aug 2025) while every docker-compose target in plane-ee had moved to the v2.5.x line during the v3.0.0 release. That release's audit was scoped to compose only -- the docs/release-v3.0.0-audit notes cover "cli/coolify/portainer commercial, podman compose + quadlets, and the aio Dockerfile build stage" and never mention helm -- so the chart was simply missed rather than deliberately held back. It matters because v1.2.0 is heavily out of date. Trivy, HIGH/CRITICAL with --ignore-unfixed, on linux/amd64: makeplane/iframely:v1.2.0 147 findings, 7 CRITICAL makeplane/iframely:v2.5.4 21 findings, 1 CRITICAL Bumped in all four places the version is spelled out, so `helm show values`, the Rancher questions form, the template fallback and the README table cannot drift apart: - values.yaml services.iframely.image - questions.yml services.iframely.image default - templates/workloads/iframely.deployment.yaml default fallback - README.md values table Safe for the chart's invocation, which is the thing worth checking: the chart sets command=[node] args=[server.js], overriding the image's entrypoint (`exec node cluster.js`), so a restructured image would break it silently. Both tags carry an identical /iframely/server.js (885 bytes) with WorkingDir /iframely and the same entrypoint, so the override still resolves. Note the chart therefore runs iframely single-process rather than clustered -- pre-existing, unchanged here. Verified: `helm lint` passes; `helm template` with the service enabled renders `image: makeplane/iframely:v2.5.4`, and an explicit services.iframely.image override still wins. Chart version 3.5.7 -> 3.5.8, matching how the recent chart fixes (#298, #299, #295) each carried their own patch bump. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (5)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. WalkthroughThe Plane Enterprise Helm chart version changes to ChangesPlane Enterprise chart update
Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: ⚪ Minimal · up to This updates the Enterprise chart’s default Iframely image to v2.5.4 and increments the chart version. The image references and override behavior are aligned, with no actionable merge risk identified. Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Linked to Plane Work Item(s) References This comment was auto-generated by Plane |
Description
The chart's
iframelydefault was still v1.2.0 (Aug 2025) while every docker-compose target inplane-eemoved to the v2.5.x line during the v3.0.0 release. That release's audit was scoped to compose only — its notes cover "cli/coolify/portainer commercial, podman compose + quadlets, and the aio Dockerfile build stage" and never mention helm — so the chart was missed rather than deliberately held back.It matters because v1.2.0 is badly out of date. Trivy, HIGH/CRITICAL with
--ignore-unfixed, onlinux/amd64:makeplane/iframely:v1.2.0makeplane/iframely:v2.5.4Bumped in all four places the version is spelled out, so
helm show values, the Rancher questions form, the template fallback and the README table cannot drift apart:values.yaml—services.iframely.imagequestions.yml—services.iframely.imagedefaulttemplates/workloads/iframely.deployment.yaml— thedefaultfallbackREADME.md— values tableWhy this is safe for the chart specifically
Worth calling out, because the chart does something the compose files don't: it sets
command: [node]/args: [server.js], which overrides the image's own entrypoint (exec node cluster.js). A restructured image would break that silently rather than loudly. I checked both tags:/iframely/server.js(885 bytes) present in bothWorkingDir(/iframely) and same entrypoint scriptSo the override still resolves. Note this means the chart runs iframely single-process rather than clustered — that's pre-existing behaviour and unchanged here, but someone may want to revisit it separately.
Chart version
3.5.7→3.5.8, matching how the recent chart fixes (#298, #299, #295) each carried their own patch bump.Type of Change
Test Scenarios
helm lint charts/plane-enterprise— passes.helm templatewithservices.iframely.enabled=trueand noenv.external_iframely_urlrendersimage: makeplane/iframely:v2.5.4.--set services.iframely.image=myrepo/iframely:customstill yieldsmyrepo/iframely:custom, so an explicit user override is unaffected.References
helm-charts-private'splane-cloudchart still defaultsservices.iframely.default_tagtov2.5.0. Separate repo, so I left it alone — happy to raise that too if wanted.🤖 Generated with Claude Code
Summary by CodeRabbit