Skip to content

chore(deps): update to helm 3.19.4 due to cve : https://github.com/helm/helm/releases/tag/v3.19.4 #25769

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
reggie-k merged 1 commit into from
Dec 22, 2025
Merged

chore(deps): update to helm 3.19.4 due to cve : https://github.com/helm/helm/releases/tag/v3.19.4 #25769

reggie-k merged 1 commit into from
Dec 22, 2025

Conversation

@stensonb
Copy link
Contributor

@stensonb stensonb commented Dec 21, 2025 •
edited
Loading

Checklist:

  • Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
  • The title of the PR states what changed and the related issues number (used for the release note).
  • The title of the PR conforms to the Title of the PR
  • I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
  • I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
  • Does this PR require documentation updates?
  • I've updated documentation as required by this PR.
  • I have signed off all my commits as required by DCO
  • I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
  • My build is green (troubleshooting builds).
  • My new feature complies with the feature status guidelines.
  • I have added a brief description of why this PR is necessary and/or what this PR solves.
  • Optional. My organization is added to USERS.md.
  • Optional. For bug fixes, I've indicated what older releases this fix should be cherry-picked into (this may or may not happen depending on risk/complexity).

@stensonb stensonb requested a review from a team as a code owner December 21, 2025 20:18
@bunnyshell
Copy link

bunnyshell bot commented Dec 21, 2025 •
edited
Loading

❌ Preview Environment deleted from Bunnyshell

Available commands (reply to this comment):

  • 🚀 /bns:deploy to deploy the environment

@stensonb stensonb force-pushed the update-helm-due-to-cve branch from cd24c24 to 0b06fe4 Compare December 21, 2025 20:21
@stensonb stensonb changed the title chore : update to helm 3.19.4 due to cve : https://github.com/helm/helm/releases/tag/v3.19.4 chore(deps) : update to helm 3.19.4 due to cve : https://github.com/helm/helm/releases/tag/v3.19.4 Dec 21, 2025
@stensonb stensonb force-pushed the update-helm-due-to-cve branch 2 times, most recently from efbf6b5 to c067fc6 Compare December 21, 2025 20:30
@stensonb stensonb changed the title chore(deps) : update to helm 3.19.4 due to cve : https://github.com/helm/helm/releases/tag/v3.19.4 chore(deps): update to helm 3.19.4 due to cve : https://github.com/helm/helm/releases/tag/v3.19.4 Dec 21, 2025
@stensonb stensonb force-pushed the update-helm-due-to-cve branch from c067fc6 to 8e769c6 Compare December 21, 2025 20:31
@stensonb
Copy link
Contributor Author

stensonb commented Dec 21, 2025

/bns:deploy

@stensonb
Copy link
Contributor Author

stensonb commented Dec 21, 2025

❗ Preview Environment deployment failed on Bunnyshell

See: Environment Details | Pipeline Logs

Available commands (reply to this comment):

* 🚀 `/bns:deploy` to redeploy the environment

* ❌ `/bns:delete` to remove the environment

/bns:deploy

@codecov
Copy link

codecov bot commented Dec 21, 2025 •
edited
Loading

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 62.60%. Comparing base (b543e18) to head (8e769c6).
⚠️ Report is 4 commits behind head on master.

Additional details and impacted files 
@@            Coverage Diff             @@
##           master   #25769      +/-   ##
==========================================
- Coverage   62.63%   62.60%   -0.03%     
==========================================
  Files         353      353              
  Lines       50159    50159              
==========================================
- Hits        31416    31403      -13     
- Misses      15725    15738      +13     
  Partials     3018     3018

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@reggie-k reggie-k merged commit 5ec3110 into argoproj:master Dec 22, 2025
30 of 31 checks passed
@reggie-k reggie-k added the cherry-pick/3.3 Candidate for cherry picking into the 3.3 release label Dec 22, 2025
argo-cd-cherry-pick-bot bot pushed a commit that referenced this pull request Dec 22, 2025
@stensonb @github-actions
chore(deps): update to helm 3.19.4 due to cve : https://github.com/he…
ff08061 
…lm/helm/releases/tag/v3.19.4 (#25769)

Signed-off-by: Bryan Stenson <bryan@siliconvortex.com>
@argo-cd-cherry-pick-bot
Copy link

argo-cd-cherry-pick-bot bot commented Dec 22, 2025

🍒 Cherry-pick PR created for 3.3: #25774

@argo-cd-cherry-pick-bot argo-cd-cherry-pick-bot bot mentioned this pull request Dec 22, 2025
Merged
reggie-k pushed a commit that referenced this pull request Dec 22, 2025
@argo-cd-cherry-pick-bot @stensonb
chore(deps): update to helm 3.19.4 due to cve : https://github.com/he…
5de1e64 
…lm/helm/releases/tag/v3.19.4 (cherry-pick #25769 for 3.3) (#25774)

Signed-off-by: Bryan Stenson <bryan@siliconvortex.com>
Co-authored-by: Bryan Stenson <bryan.stenson@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@reggie-k reggie-k reggie-k approved these changes

Assignees

No one assigned

Labels

cherry-pick/3.3 Candidate for cherry picking into the 3.3 release

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@stensonb @reggie-k