chore: replace manual helm registry login steps with step-security/docker-login-action - #5132
Conversation
📝 WalkthroughSummary by CodeRabbit
WalkthroughThe Helm release workflow replaces shell-based GHCR and Docker Hub authentication with conditional Docker login actions, and changes the Docker Hub OCI destination for the packaged Helm chart. ChangesHelm release registry flow
Estimated code review effort: 1 (Trivial) | ~5 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
This stack of pull requests is managed by Graphite. Learn more about stacking. |
helm registry login steps with step-security/docker-login-action
Confidence Score: 5/5This looks safe to merge.
Important Files Changed
Reviews (2): Last reviewed commit: "fix: auth on docker and github for helm ..." | Re-trigger Greptile |
b2218f7 to
c0d8545
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 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 @.github/workflows/helm-release.yml:
- Around line 141-153: Remove continue-on-error: true from the Docker Hub login
step and both subsequent helm push steps in the release workflow, while
preserving their existing conditions and actions so authentication or
publication failures fail the workflow.
🪄 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: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro Plus
Run ID: 58b893e8-cb51-4bc9-b89e-bd1041e0c875
📒 Files selected for processing (1)
.github/workflows/helm-release.yml
Merge activity
|
* origin/dev: (79 commits) chore: add `helm-update` Claude skill for syncing Helm chart with `config.schema.json` (maximhq#5144) fix: web search options to google search mapping in gemini api (maximhq#5139) feat: add `postgresql.external.port` string support and `bifrost.mcp.toolGroups[*].id` to Helm chart (maximhq#5143) fix: parse `SecretVar` JSON with `ref`/`env_var` fields even when `value` is absent (maximhq#5146) Revert "fix: less strict unmarshalling for secret var (maximhq#4723)" (maximhq#5145) fix: max reasoning effort in openai (maximhq#5130) chore: replace manual `helm registry login` steps with `step-security/docker-login-action` (maximhq#5132) fix: support GA transcription-type sessions in POST /v1/realtime/client_secrets (maximhq#5092) community: add Xquik to MCP library (maximhq#5069) fix: warn callers not to truncate the #t= temp-token fragment on MCP inline-auth links (maximhq#5104) chore: build fix in core (maximhq#5129) fix: never persist masked provider key previews (maximhq#5106) Filter out provider-level keys from selector in prompt manager (maximhq#5018) fix: show user popover when `userInfo` exists and include `preferred_username` as display name fallback (maximhq#5098) fix: use `AutoMigrate` and add `runner_id`/`created_by_user_id` columns to sidekiq table migration (maximhq#5085) dds new harness skill and updates based on merged PRs (maximhq#5126) dds new harness skill and updates based on merged PRs (maximhq#5123) Add Trendshift badge to README (maximhq#5124) fix: make tracing span lookup nil-safe to prevent panic on streaming errors (maximhq#4896) Revert "fix: synthesize per-query rerank usage for Bedrock and Vertex (maximhq#4322)" (maximhq#5122) ...
…/docker-login-action` (#5132) ## Summary Replaces manual `helm registry login` shell commands with the `step-security/docker-login-action` for authenticating to both GitHub Container Registry (GHCR) and Docker Hub during Helm chart releases. ## Changes - Replaced inline `helm registry login` shell commands for GHCR and Docker Hub with `step-security/docker-login-action@870af644803bf9f204aed474adbad2958fec048b` (v4.1.0) - Removed `continue-on-error: true` from both login steps, meaning login failures will now correctly fail the workflow rather than silently continuing - Credentials are now passed directly via the action's `with` inputs rather than environment variables ## Type of change - [ ] Bug fix - [ ] Feature - [ ] Refactor - [ ] Documentation - [x] Chore/CI ## Affected areas - [ ] Core (Go) - [ ] Transports (HTTP) - [ ] Providers/Integrations - [ ] Plugins - [ ] UI (React) - [ ] Docs ## How to test Trigger a Helm release workflow and verify that both GHCR and Docker Hub login steps complete successfully and the chart is pushed as an OCI artifact. ## Breaking changes - [ ] Yes - [x] No ## Security considerations Using the pinned `step-security/docker-login-action` action (pinned to a full commit SHA) is a supply chain security improvement over manually invoking `helm registry login` in shell. Removing `continue-on-error: true` ensures that credential failures are surfaced immediately rather than allowing the workflow to proceed with potentially unauthenticated pushes. ## Checklist - [x] I read `docs/contributing/README.md` and followed the guidelines - [ ] I added/updated tests where appropriate - [ ] I updated documentation where needed - [x] I verified builds succeed (Go and UI) - [x] I verified the CI pipeline passes locally if applicable
…/docker-login-action` (maximhq#5132) ## Summary Replaces manual `helm registry login` shell commands with the `step-security/docker-login-action` for authenticating to both GitHub Container Registry (GHCR) and Docker Hub during Helm chart releases. ## Changes - Replaced inline `helm registry login` shell commands for GHCR and Docker Hub with `step-security/docker-login-action@870af644803bf9f204aed474adbad2958fec048b` (v4.1.0) - Removed `continue-on-error: true` from both login steps, meaning login failures will now correctly fail the workflow rather than silently continuing - Credentials are now passed directly via the action's `with` inputs rather than environment variables ## Type of change - [ ] Bug fix - [ ] Feature - [ ] Refactor - [ ] Documentation - [x] Chore/CI ## Affected areas - [ ] Core (Go) - [ ] Transports (HTTP) - [ ] Providers/Integrations - [ ] Plugins - [ ] UI (React) - [ ] Docs ## How to test Trigger a Helm release workflow and verify that both GHCR and Docker Hub login steps complete successfully and the chart is pushed as an OCI artifact. ## Breaking changes - [ ] Yes - [x] No ## Security considerations Using the pinned `step-security/docker-login-action` action (pinned to a full commit SHA) is a supply chain security improvement over manually invoking `helm registry login` in shell. Removing `continue-on-error: true` ensures that credential failures are surfaced immediately rather than allowing the workflow to proceed with potentially unauthenticated pushes. ## Checklist - [x] I read `docs/contributing/README.md` and followed the guidelines - [ ] I added/updated tests where appropriate - [ ] I updated documentation where needed - [x] I verified builds succeed (Go and UI) - [x] I verified the CI pipeline passes locally if applicable
…/docker-login-action` (maximhq#5132) ## Summary Replaces manual `helm registry login` shell commands with the `step-security/docker-login-action` for authenticating to both GitHub Container Registry (GHCR) and Docker Hub during Helm chart releases. ## Changes - Replaced inline `helm registry login` shell commands for GHCR and Docker Hub with `step-security/docker-login-action@870af644803bf9f204aed474adbad2958fec048b` (v4.1.0) - Removed `continue-on-error: true` from both login steps, meaning login failures will now correctly fail the workflow rather than silently continuing - Credentials are now passed directly via the action's `with` inputs rather than environment variables ## Type of change - [ ] Bug fix - [ ] Feature - [ ] Refactor - [ ] Documentation - [x] Chore/CI ## Affected areas - [ ] Core (Go) - [ ] Transports (HTTP) - [ ] Providers/Integrations - [ ] Plugins - [ ] UI (React) - [ ] Docs ## How to test Trigger a Helm release workflow and verify that both GHCR and Docker Hub login steps complete successfully and the chart is pushed as an OCI artifact. ## Breaking changes - [ ] Yes - [x] No ## Security considerations Using the pinned `step-security/docker-login-action` action (pinned to a full commit SHA) is a supply chain security improvement over manually invoking `helm registry login` in shell. Removing `continue-on-error: true` ensures that credential failures are surfaced immediately rather than allowing the workflow to proceed with potentially unauthenticated pushes. ## Checklist - [x] I read `docs/contributing/README.md` and followed the guidelines - [ ] I added/updated tests where appropriate - [ ] I updated documentation where needed - [x] I verified builds succeed (Go and UI) - [x] I verified the CI pipeline passes locally if applicable

Summary
Replaces manual
helm registry loginshell commands with thestep-security/docker-login-actionfor authenticating to both GitHub Container Registry (GHCR) and Docker Hub during Helm chart releases.Changes
helm registry loginshell commands for GHCR and Docker Hub withstep-security/docker-login-action@870af644803bf9f204aed474adbad2958fec048b(v4.1.0)continue-on-error: truefrom both login steps, meaning login failures will now correctly fail the workflow rather than silently continuingwithinputs rather than environment variablesType of change
Affected areas
How to test
Trigger a Helm release workflow and verify that both GHCR and Docker Hub login steps complete successfully and the chart is pushed as an OCI artifact.
Breaking changes
Security considerations
Using the pinned
step-security/docker-login-actionaction (pinned to a full commit SHA) is a supply chain security improvement over manually invokinghelm registry loginin shell. Removingcontinue-on-error: trueensures that credential failures are surfaced immediately rather than allowing the workflow to proceed with potentially unauthenticated pushes.Checklist
docs/contributing/README.mdand followed the guidelines