Skip to content
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.

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

feat(argo-apps): Update Argo Rollouts from 1.7.0 to 1.7.2 #1340

Merged
merged 2 commits into from
Dec 11, 2024

Conversation

hairmare
Copy link
Contributor

@hairmare hairmare commented Nov 22, 2024

Description

Updates Argo Rollouts to 1.7.2 for a bunch of fixes and broader compat.

Issues

Checklist

  • This PR contains a description of the changes I'm making
  • I updated the version in Chart.yaml
  • I updated the changelog with an artifacthub.io/changes annotation in Chart.yaml, check the example in the documentation.
  • I updated applicable README.md files using pre-commit run
  • I documented any high-level concepts I'm introducing in docs/
  • CI is currently green and this is ready for review
  • I am ready to test changes after they are applied and released

@github-actions github-actions bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Nov 22, 2024
@hairmare hairmare marked this pull request as ready for review November 22, 2024 16:56
@hairmare hairmare requested a review from a team as a code owner November 22, 2024 16:56
@hairmare hairmare force-pushed the feat/argo-apps/argo-rollouts/update-from-2.36.0-to-2.38.0 branch from ac523bd to d83dac8 Compare November 25, 2024 08:08
@hairmare hairmare force-pushed the feat/argo-apps/argo-rollouts/update-from-2.36.0-to-2.38.0 branch from d83dac8 to a92edfb Compare November 29, 2024 15:57
@eyenx eyenx merged commit d013a55 into main Dec 11, 2024
3 checks passed
@eyenx eyenx deleted the feat/argo-apps/argo-rollouts/update-from-2.36.0-to-2.38.0 branch December 11, 2024 17:29
@eyenx
Copy link
Member

eyenx commented Dec 11, 2024

Only merged this because after @fugal-dy merged this PR #1348 it did not trigger a release action. So I merged this myself to make it trigger the release workflow and release both charts. We need to figure out why the release action wasn't triggered on main. @hairmare

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants