🌱 Update github-actions group #111
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![cluster-stack-bot[bot]](https://avatars.githubusercontent.com/u/63697494?s=60&v=4){kind=small}
cluster-stack-bot
bot
force-pushed
the
renovate/github-actions
branch
from
c902ee9
to
d828e02
Compare
| datasource | package | from | to | | ----------- | ----------------------------------------- | ------ | ------ | | github-tags | docker/build-push-action | v5.1.0 | v5.2.0 | | github-tags | kubernetes-sigs/kubebuilder-release-tools | v0.3.0 | v0.4.3 | | github-tags | sigstore/cosign-installer | v3.0.5 | v3.4.0 |
kranurag7
force-pushed
the
renovate/github-actions
branch
from
d828e02
to
8b1ffb6
Compare
kranurag7
approved these changes
Mar 13, 2024
kranurag7
added a commit
that referenced
this pull request
Apr 24, 2024
🌱 Update github-actions group
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
f4c6bf6->f2acddf4a13e50->af5a7edv5.1.0->v5.2.0v0.3.0->v0.4.3v3.0.5->v3.4.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
docker/build-push-action (docker/build-push-action)
v5.2.0Compare Source
outputsinput by @crazy-max in https://github.com/docker/build-push-action/pull/1074Full Changelog: docker/build-push-action@v5.1.0...v5.2.0
kubernetes-sigs/kubebuilder-release-tools (kubernetes-sigs/kubebuilder-release-tools)
v0.4.3Compare Source
What's Changed
Full Changelog: kubernetes-sigs/kubebuilder-release-tools@v0.4.2...v0.4.3
v0.4.2Compare Source
What's Changed
Full Changelog: kubernetes-sigs/kubebuilder-release-tools@v0.4.1...v0.4.2
v0.4.1Compare Source
What's Changed
New Contributors
Full Changelog: kubernetes-sigs/kubebuilder-release-tools@v0.4.0...v0.4.1
v0.4.0Compare Source
What's Changed
New Contributors
Full Changelog: kubernetes-sigs/kubebuilder-release-tools@v0.3.0...v0.4.0
sigstore/cosign-installer (sigstore/cosign-installer)
v3.4.0Compare Source
What's Changed
New Contributors
Full Changelog: sigstore/cosign-installer@v3...v3.4.0
v3.3.0Compare Source
What's Changed
Full Changelog: sigstore/cosign-installer@v3.2.0...v3.3.0
v3.2.0Compare Source
Note: This release comes with a fix for CVE-2023-46737 described in this Github Security Advisory. Please upgrade to this release ASAP
see https://github.com/sigstore/cosign/releases/tag/v2.2.1
What's Changed
New Contributors
Full Changelog: sigstore/cosign-installer@v3...v3.2.0
v3.1.2Compare Source
What's Changed
New Contributors
Full Changelog: sigstore/cosign-installer@v3...v3.1.2
v3.1.1Compare Source
What's Changed
Full Changelog: sigstore/cosign-installer@v3.1.0...v3.1.1
v3.1.0Compare Source
What's Changed
New Contributors
Full Changelog: sigstore/cosign-installer@v3.0.5...v3.1.0
Configuration
📅 Schedule: Branch creation - "on monday" in timezone Europe/Berlin, 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.