chore(deps): update helm release argo-rollouts to v2.38.0

[renovate]

This PR contains the following updates:

Package	Update	Change
argo-rollouts	minor	2.37.8 -> 2.38.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

argoproj/argo-helm (argo-rollouts)

v2.38.0

Compare Source

A Helm chart for Argo Rollouts

What's Changed

• fix(argo-rollouts): Change type of trafficRouterPlugins and trafficRouterPlugins as list by @​taer in https://github.com/argoproj/argo-helm/pull/3036

Full Changelog: argoproj/argo-helm@argo-cd-7.7.5...argo-rollouts-2.38.0

---

Configuration

📅 Schedule: 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.

[sourcery-ai]

Reviewer's Guide by Sourcery

This PR updates the Argo Rollouts Helm chart dependency from version 2.37.8 to 2.38.0. The update includes a fix for the trafficRouterPlugins configuration by changing its type to a list format.

ER diagram for updated trafficRouterPlugins configuration

erDiagram
    ARGO_ROLLOUTS {
        string name
        string version
        list trafficRouterPlugins
    }

    ARGO_ROLLOUTS ||--o{ TRAFFIC_ROUTER_PLUGINS : has
    TRAFFIC_ROUTER_PLUGINS {
        string pluginName
        string pluginType
    }

Loading

File-Level Changes

Change	Details	Files
Update Argo Rollouts Helm chart version	Bump argo-rollouts version from 2.37.8 to 2.38.0 Update Chart.lock to reflect new dependency version	ops/Helm/addons/argo/argo-rollouts/Chart.yaml ops/Helm/addons/argo/argo-rollouts/Chart.lock

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, renovate[bot]!). We assume it knows what it's doing!

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud