-
Notifications
You must be signed in to change notification settings - Fork 17
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(deps): update all non-major dependencies #294
Conversation
Interesting, it looks like there was an update of policy-reporter |
I would put this PR on hold, and address that once the 1.7.0 release is done |
Moving to block until we release |
042cb81
to
9e69a62
Compare
moving back to pending review, since 1.7.0 is out |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've updated the chart-values.yaml
file bumping the container image tag as well. Therefore, the CI will pass.
LGTM.
f77d11b
to
7b69bf1
Compare
Updates the chart-values.yaml file changing the policy reporter tag to follow the update in the values.yaml done by renovate bot Signed-off-by: José Guilherme Vanz <[email protected]>
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. ⚠ Warning: custom changes will be lost. |
On #294, the bot bumped of policy-reporter-ui, where it got bumped to v1.15.1. Turns out that 1.15.1 tag is 2 years old, and looks like a mistake on tagging, as it is between 0.15.0 and 0.15.1 in the timeline. See: https://github.com/orgs/kyverno/packages/container/policy-reporter-ui/10126783?tag=1.15.1 Signed-off-by: Martin Kravec <[email protected]>
On #294, the bot bumped of policy-reporter-ui, where it got bumped to v1.15.1. Turns out that 1.15.1 tag is 2 years old, and looks like a mistake on tagging, as it is between 0.15.0 and 0.15.1 in the timeline. See: https://github.com/orgs/kyverno/packages/container/policy-reporter-ui/10126783?tag=1.15.1 Signed-off-by: Víctor Cuadrado Juan <[email protected]>
On #294, the bot bumped of policy-reporter-ui, where it got bumped to v1.15.1. Turns out that 1.15.1 tag is 2 years old, and looks like a mistake on tagging, as it is between 0.15.0 and 0.15.1 in the timeline. See: https://github.com/orgs/kyverno/packages/container/policy-reporter-ui/10126783?tag=1.15.1 Signed-off-by: Víctor Cuadrado Juan <[email protected]>
This PR contains the following updates:
2.15.4
->2.16.0
1.8.4
->1.15.1
2.19.4
->2.20.0
v2.39.0
->v2.41.0
⚠ Dependency Lookup Warnings ⚠
Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.
Release Notes
kyverno/policy-reporter (policy-reporter)
v2.20.0
Compare Source
updatecli/updatecli-action (updatecli/updatecli-action)
v2.41.0
: 🌈Compare Source
Changes
Contributors
@github-actions and @github-actions[bot]
v2.40.0
: 🌈Compare Source
Changes
Contributors
@github-actions, @github-actions[bot] and @olblak
Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.