Skip to content

chore(deps): update azure/setup-helm action to v5#68

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/azure-setup-helm-5.x
Open

chore(deps): update azure/setup-helm action to v5#68
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/azure-setup-helm-5.x

Conversation

@renovate

@renovate renovate Bot commented Mar 23, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
azure/setup-helm action major v4v5

Release Notes

azure/setup-helm (azure/setup-helm)

v5.0.0

Compare Source

Changed

v5

Compare Source


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot force-pushed the renovate/azure-setup-helm-5.x branch from 88b00b6 to 61feb5e Compare April 15, 2026 09:04
@renovate renovate Bot force-pushed the renovate/azure-setup-helm-5.x branch from 61feb5e to 6856e4a Compare May 28, 2026 21:14

@doubleword-code doubleword-code Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary

This PR updates the azure/setup-helm GitHub Action from v4 to v5 in two workflow files (.github/workflows/ci.yml and .github/workflows/release-please.yml). Verdict: Ready to approve — this is a straightforward dependency update with no breaking changes affecting the current usage pattern.

Research notes

I reviewed the official azure/setup-helm repository and its CHANGELOG:

  • v5.0.0 release date: March 23, 2026
  • Primary change: Node.js runtime updated from node20 to node24 (PR #259)
  • Additional changes: Multiple dependency bumps including undici, minimatch, js-yaml, glob, @actions/http-client (security and maintenance updates)
  • No breaking API changes: The action's inputs remain unchanged; the version parameter continues to work as before

The current usage pattern (uses: azure/setup-helm@v5 with version: "3.13.0") is valid and follows the documented usage in the action's README.

Suggested next steps

  1. Merge this PR — the update is safe and includes beneficial security patches.
  2. (Optional follow-up) Consider pinning the action to a specific version tag (e.g., @v5.0.0) instead of the floating @v5 major-version tag if you want stricter reproducibility. This is a common practice for security-conscious workflows, though using major-version tags is also widely accepted when the action maintainer follows semantic versioning.

General findings

Observation only (not a blocker): Both workflows specify Helm version 3.13.0, which is older than the action's fallback default (currently 3.18.3 per the README). The action will attempt to fetch the requested version, but if that fails, it will silently use the fallback. This is pre-existing behavior and not introduced by this PR, but worth being aware of in case of unexpected Helm version mismatches during CI runs.

All changed lines have been verified against the diff. No issues found.

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.

0 participants