Bug: Stable release becomes outdated very quickly due to hard coding
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- helm, typescript
Research direction
Start in src/run.ts at the hard-coded stableHelmVersion referenced by the issue, and inspect how the GitHub Action selects the default Helm release. Confirm the intended naming and version behavior against current Helm releases, then verify that the action no longer installs an outdated default and supports the syntax discussed in #187.
Written by the indexing model from the issue text.
Description
What happened?
You appear to set a stableHelmVersion in run.ts. That's problematic because the stable version changes frequently so this action quickly ends up with an outdated stable version.
https://github.com/Azure/setup-helm/blob/df342a2656c018d52484e7d07ce33e4ade6254bb/src/run.ts#L13
Currently, the "stable" version points at 3.13.3 which has not been the latest stable for 1.5 years (since January 2024): https://github.com/helm/helm/releases/tag/v3.14.0
You should probably call it defaultHelmVersion as stable is misleading.
Also, this version should be updated with every release to not have too much of a gap between actual upstream stable and this action's "stable".
Using old versions means that newly introduced syntax will not work, e.g. --skip-schema-validation, see #187
Version
- I am using the latest version
Runner
default
Relevant log output
NA
- Dominant language
- TypeScript
- Stars
- 191
- Forks
- 79
- Avg merge
- 17d 9h
- Merged PRs (30d)
- 1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/setup-helm
-
bug
Azure/setup-helm#270 · 5 reactions · 1 assignee ·
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
Azure/setup-helm#249 · 1 reaction ·
-
Feature Request: Add semver range support to allow installing Helm v3.x or any major/minor version Open
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Azure/setup-helm#242 · 1 comment · 2 reactions ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 58/100
Azure/setup-helm#241 · 2 comments · 2 reactions ·
-
Bug: azure/setup-helm@v4 Automatically Installing Helm v4.0.1 Causing Plugin Verification Failure Openbug
Difficulty 3/5 1-2 days Newbie friendliness 42/100
Azure/setup-helm#239 ·
All issues in Azure/setup-helm
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100