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

Update docker/metadata-action action to v5 #413

Merged
merged 1 commit into from
Jul 22, 2024

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Sep 16, 2023

Mend Renovate

This PR contains the following updates:

Package Type Update Change
docker/metadata-action action major v4 -> v5

Warning

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


Release Notes

docker/metadata-action (docker/metadata-action)

v5

Compare Source


Configuration

📅 Schedule: Branch creation - "every weekend" (UTC), 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.

@openshift-ci
Copy link

openshift-ci bot commented Sep 16, 2023

Hi @renovate[bot]. Thanks for your PR.

I'm waiting for a ComplianceAsCode member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@renovate renovate bot force-pushed the renovate/docker-metadata-action-5.x branch from 2c5ee0c to 5ef0940 Compare September 20, 2023 16:55
@renovate renovate bot changed the title chore(deps): update docker/metadata-action action to v5 Update docker/metadata-action action to v5 Jan 16, 2024
@renovate renovate bot force-pushed the renovate/docker-metadata-action-5.x branch from 5ef0940 to 3632794 Compare January 26, 2024 05:19
Copy link

🤖 To deploy this PR, run the following command:

make catalog-deploy CATALOG_IMG=ghcr.io/complianceascode/compliance-operator-catalog:413

@rhmdnd
Copy link

rhmdnd commented Feb 2, 2024

/retest-required

@renovate renovate bot force-pushed the renovate/docker-metadata-action-5.x branch from 3632794 to 3c6720e Compare March 15, 2024 23:15
@renovate renovate bot force-pushed the renovate/docker-metadata-action-5.x branch from 3c6720e to c6e99e4 Compare May 2, 2024 15:26
@rhmdnd
Copy link

rhmdnd commented May 3, 2024

/retest-required

Serial tests should be unblocked now.

@renovate renovate bot force-pushed the renovate/docker-metadata-action-5.x branch from c6e99e4 to 9550718 Compare June 7, 2024 13:01
@renovate renovate bot force-pushed the renovate/docker-metadata-action-5.x branch from 9550718 to a82a6ea Compare July 12, 2024 17:54
Copy link

🤖 To deploy this PR, run the following command:

make catalog-deploy CATALOG_IMG=ghcr.io/complianceascode/compliance-operator-catalog:413

@rhmdnd
Copy link

rhmdnd commented Jul 15, 2024

/test e2e-rosa

Failed to deploy rosa cluster (unrelated to the change in review).

Copy link

openshift-ci bot commented Jul 19, 2024

@renovate: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-rosa a82a6ea link true /test e2e-rosa

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@renovate renovate bot force-pushed the renovate/docker-metadata-action-5.x branch from a82a6ea to 7bb4dab Compare July 22, 2024 14:07
Copy link

🤖 To deploy this PR, run the following command:

make catalog-deploy CATALOG_IMG=ghcr.io/complianceascode/compliance-operator-catalog:413

Copy link

@rhmdnd rhmdnd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

Copy link

openshift-ci bot commented Jul 22, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: renovate[bot], rhmdnd

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-bot openshift-merge-bot bot merged commit a1312eb into master Jul 22, 2024
11 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the renovate/docker-metadata-action-5.x branch July 22, 2024 21:28
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.

1 participant