refactor(hub): pin hub version to 0.8.43#130
Conversation
📝 WalkthroughWalkthroughUpdates the Helm chart for flame-hub to pin the container image version from ChangesImage Version Update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
charts/flame-hub/values.yaml (1)
176-176: ⚡ Quick winConsider pinning the authup version for consistency.
While the main hub image is now pinned to
0.8.44, the authup subchart still usestag: "latest"(line 176). For consistency and to ensure fully reproducible deployments across all components, consider pinning this version as well.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@charts/flame-hub/values.yaml` at line 176, The authup subchart currently uses a floating image tag ("tag: \"latest\"") which prevents reproducible deployments; update the authup subchart's image tag to a fixed version string (match the hub's pinned style, e.g., "0.8.44" or the appropriate authup release) by replacing the value for the key tag under the authup block in values.yaml so the authup image is pinned rather than "latest".
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@charts/flame-hub/values.yaml`:
- Line 59: The values.yaml currently pins the Flame Hub image tag to 0.8.44
which appears missing on GHCR (image ghcr.io/privateaim/hub:0.8.44); either
publish the missing 0.8.44 tag to GHCR or update charts/flame-hub/values.yaml to
a published tag (or a digest) so deployments won't 404 on pull, and while here
consider pinning authup's image (currently using latest) to a specific tag for
consistency.
---
Nitpick comments:
In `@charts/flame-hub/values.yaml`:
- Line 176: The authup subchart currently uses a floating image tag ("tag:
\"latest\"") which prevents reproducible deployments; update the authup
subchart's image tag to a fixed version string (match the hub's pinned style,
e.g., "0.8.44" or the appropriate authup release) by replacing the value for the
key tag under the authup block in values.yaml so the authup image is pinned
rather than "latest".
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: a0be1d32-a192-45bd-894f-3e88fbb34356
📒 Files selected for processing (1)
charts/flame-hub/values.yaml
testing flux pr previews
Summary by CodeRabbit