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

chore(bitnami/redis-exporter): Update public.ecr.aws/bitnami/redis-exporter Docker tag to v1.67.0 #3104

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

argoproj-renovate[bot]
Copy link
Contributor

@argoproj-renovate argoproj-renovate bot commented Jan 4, 2025

This PR contains the following updates:

Package Update Change
public.ecr.aws/bitnami/redis-exporter (source) minor 1.58.0 -> 1.67.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 is behind base branch, 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 has been generated by Renovate Bot.

@yu-croco
Copy link
Collaborator

yu-croco commented Jan 4, 2025

#3072 made this PR. It seems that we needed to enhance https://github.com/argoproj/argo-helm/blob/main/renovate.json at the same time. 🙃

@argoproj-renovate argoproj-renovate bot force-pushed the renovate/public.ecr.aws-bitnami-redis-exporter-1.x branch 2 times, most recently from 59f524e to 0e67360 Compare January 5, 2025 07:14
@argoproj-renovate argoproj-renovate bot changed the title chore(deps): update public.ecr.aws/bitnami/redis-exporter docker tag to v1.67.0 chore(bitnami/redis-exporter): Update public.ecr.aws/bitnami/redis-exporter Docker tag to v1.67.0 Jan 5, 2025
@argoproj-renovate
Copy link
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: charts/argo-cd/values.yaml
Command failed: ./scripts/renovate-bump-version.sh public.ecr.aws/bitnami/redis-exporter
grep: charts/public.ecr.aws/bitnami/redis-exporter/Chart.yaml: No such file or directory
sed: can't read charts/public.ecr.aws/bitnami/redis-exporter/Chart.yaml: No such file or directory
grep: charts/public.ecr.aws/bitnami/redis-exporter/Chart.yaml: No such file or directory
sed: can't read charts/public.ecr.aws/bitnami/redis-exporter/Chart.yaml: No such file or directory
./scripts/renovate-bump-version.sh: line 30: charts/public.ecr.aws/bitnami/redis-exporter/Chart.yaml: No such file or directory
cat: charts/public.ecr.aws/bitnami/redis-exporter/Chart.yaml: No such file or directory

@yu-croco
Copy link
Collaborator

yu-croco commented Jan 5, 2025

🫠

@tico24
Copy link
Member

tico24 commented Jan 5, 2025

Bitnami’s charts went oci-only about a month ago. Did we update to reflect that? If not, this would explain the error.

@yu-croco
Copy link
Collaborator

yu-croco commented Jan 5, 2025

There was a PR to run Renovate against tags in values.yaml and we needed to handle scripts for it.

But here is the result. 🫠
Need to modify scripts for tags in values.yaml (or stop supporting Renovate to tags in values.yaml).

@tico24
Copy link
Member

tico24 commented Jan 5, 2025

It looks like https://github.com/argoproj/argo-helm/blob/main/scripts/renovate-bump-version.sh Is only designed to look at our internal charts, not third party dependencies. It looks like renovate it running this script expecting to be able to change the upstream chart.yaml.

@tico24
Copy link
Member

tico24 commented Jan 5, 2025

The script needs to be refactored so that it understands that it’s changing our argocd values file and not the third party chart.

@tico24
Copy link
Member

tico24 commented Jan 5, 2025

The issue lies in the depname variable and how it’s then used.

@yu-croco
Copy link
Collaborator

yu-croco commented Jan 5, 2025

I will fix the script in #3106 🙋

@mkilchhofer
Copy link
Member

mkilchhofer commented Jan 5, 2025

The initial PR (#3072) about dependencies inside values.yaml introduced a new PR naming pattern.

Our idea was to name PRs according to conventional commits using the chart names as the scopes:

  • feat(argo-cd): Bump Argo CD
  • chore(argo-cd): Bump redis-exporter
  • chore(argo-workflows): Blah blah

Now we have the dependency in the conventional commit scope. I think we should address this as well.

Ref in contributors guide:
https://github.com/argoproj/argo-helm/blob/main/CONTRIBUTING.md#pull-request-title-linting

@argoproj-renovate argoproj-renovate bot force-pushed the renovate/public.ecr.aws-bitnami-redis-exporter-1.x branch 6 times, most recently from 0e49066 to c3ac910 Compare January 10, 2025 11:14
…porter Docker tag to v1.67.0

Signed-off-by: argoproj-renovate[bot] <161757507+argoproj-renovate[bot]@users.noreply.github.com>
@argoproj-renovate argoproj-renovate bot force-pushed the renovate/public.ecr.aws-bitnami-redis-exporter-1.x branch from c3ac910 to 12c3e29 Compare January 11, 2025 11:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants