fix(deps): update non-minor dependencies #15
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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/non-minor-deps
branch
from
71f1cf7 to
69d76de
Compare
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
renovate
bot
force-pushed
the
renovate/non-minor-deps
branch
from
69d76de to
9136d55
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/non-minor-deps
branch
2 times, most recently
from
edc6bf0 to
9ca3886
Compare
renovate
bot
force-pushed
the
renovate/non-minor-deps
branch
5 times, most recently
from
2f72222 to
92cdbce
Compare
renovate
bot
force-pushed
the
renovate/non-minor-deps
branch
7 times, most recently
from
396919e to
0b57ad6
Compare
renovate
bot
force-pushed
the
renovate/non-minor-deps
branch
6 times, most recently
from
9943007 to
c516f47
Compare
renovate
bot
force-pushed
the
renovate/non-minor-deps
branch
4 times, most recently
from
ab071f1 to
9064961
Compare
renovate
bot
force-pushed
the
renovate/non-minor-deps
branch
10 times, most recently
from
faaffce to
8371a41
Compare
renovate
bot
force-pushed
the
renovate/non-minor-deps
branch
9 times, most recently
from
ab53c3b to
6532572
Compare
renovate
bot
force-pushed
the
renovate/non-minor-deps
branch
4 times, most recently
from
4d9de84 to
079079a
Compare
renovate
bot
force-pushed
the
renovate/non-minor-deps
branch
from
079079a to
db39895
Compare
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. |
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:
v3.9.0->v3.9.2v0.3.55->v0.3.593854680->aea2e32v0.16.2->v0.16.5Release Notes
getsops/sops (github.com/getsops/sops/v3)
v3.9.2Compare Source
Installation
To install
sops, download one of the pre-built binaries provided for your platform from the artifacts attached to this release.For instance, if you are using Linux on an AMD64 architecture:
Verify checksums file signature
The checksums file provided within the artifacts attached to this release is signed using Cosign with GitHub OIDC. To validate the signature of this file, run the following commands:
Verify binary integrity
To verify the integrity of the downloaded binary, you can utilize the checksums file after having validated its signature:
##### Verify the binary using the checksums file sha256sum -c sops-v3.9.2.checksums.txt --ignore-missingVerify artifact provenance
The SLSA provenance of the binaries, packages, and SBOMs can be found within the artifacts associated with this release. It is presented through an in-toto link metadata file named
sops-v3.9.2.intoto.jsonl. To verify the provenance of an artifact, you can utilize theslsa-verifiertool:Container Images
The
sopsbinaries are also available as container images, based on Debian (slim) and Alpine Linux. The Debian-based container images include any dependencies which may be required to make use of certain key services, such as GnuPG, AWS KMS, Azure Key Vault, and Google Cloud KMS. The Alpine-based container images are smaller in size, but do not include these dependencies.These container images are available for the following architectures:
linux/amd64andlinux/arm64.GitHub Container Registry
ghcr.io/getsops/sops:v3.9.2ghcr.io/getsops/sops:v3.9.2-alpineQuay.io
quay.io/getsops/sops:v3.9.2quay.io/getsops/sops:v3.9.2-alpineVerify container image signature
The container images are signed using Cosign with GitHub OIDC. To validate the signature of an image, run the following command:
Verify container image provenance
The container images include SLSA provenance attestations. For more information around the verification of this, please refer to the
slsa-verifierdocumentation.Software Bill of Materials
The Software Bill of Materials (SBOM) for each binary is accessible within the artifacts enclosed with this release. It is presented as an SPDX JSON file, formatted as
<binary>.spdx.sbom.json.What's Changed
New Contributors
Full Changelog: getsops/sops@v3.9.1...v3.9.2
v3.9.1Compare Source
Installation
To install
sops, download one of the pre-built binaries provided for your platform from the artifacts attached to this release.For instance, if you are using Linux on an AMD64 architecture:
Verify checksums file signature
The checksums file provided within the artifacts attached to this release is signed using Cosign with GitHub OIDC. To validate the signature of this file, run the following commands:
Verify binary integrity
To verify the integrity of the downloaded binary, you can utilize the checksums file after having validated its signature:
### Verify the binary using the checksums file sha256sum -c sops-v3.9.1.checksums.txt --ignore-missingVerify artifact provenance
The SLSA provenance of the binaries, packages, and SBOMs can be found within the artifacts associated with this release. It is presented through an in-toto link metadata file named
sops-v3.9.1.intoto.jsonl. To verify the provenance of an artifact, you can utilize theslsa-verifiertool:Container Images
The
sopsbinaries are also available as container images, based on Debian (slim) and Alpine Linux. The Debian-based container images include any dependencies which may be required to make use of certain key services, such as GnuPG, AWS KMS, Azure Key Vault, and Google Cloud KMS. The Alpine-based container images are smaller in size, but do not include these dependencies.These container images are available for the following architectures:
linux/amd64andlinux/arm64.GitHub Container Registry
ghcr.io/getsops/sops:v3.9.1ghcr.io/getsops/sops:v3.9.1-alpineQuay.io
quay.io/getsops/sops:v3.9.1quay.io/getsops/sops:v3.9.1-alpineVerify container image signature
The container images are signed using Cosign with GitHub OIDC. To validate the signature of an image, run the following command:
Verify container image provenance
The container images include SLSA provenance attestations. For more information around the verification of this, please refer to the
slsa-verifierdocumentation.Software Bill of Materials
The Software Bill of Materials (SBOM) for each binary is accessible within the artifacts enclosed with this release. It is presented as an SPDX JSON file, formatted as
<binary>.spdx.sbom.json.What's Changed
--shamir-secret-sharing-thresholdby @felixfontein in https://github.com/getsops/sops/pull/1608--configbeing ignored byloadConfigby @lopter in https://github.com/getsops/sops/pull/1613New Contributors
Full Changelog: getsops/sops@v3.9.0...v3.9.1
sap/component-operator-runtime (github.com/sap/component-operator-runtime)
v0.3.59Compare Source
v0.3.58Compare Source
This release is a bugfix release for the
clmcli. So far, while applying or deleting a release,clmwas aborting immediately if an error occurred. This is not very convenient. At least in some ephemeral error situations, it should behave in a more resilient way. So, with this release,clmtries to recognise such ephemeral errors (for example 409 - Conflict responses from the API server), and retries the failing operation a couple of times.v0.3.57Compare Source
v0.3.56Compare Source
Enhancements
A new flag
--create-namespacewas added toclm apply. If specified the specified release namespace will be auto-created if missing. Note that in that case, the namespace is not part of the release inventory. In particular, it will not be deleted if the component gets deleted.kubernetes-sigs/controller-tools (sigs.k8s.io/controller-tools)
v0.16.5Compare Source
What's Changed
Dependencies
Full Changelog: kubernetes-sigs/controller-tools@v0.16.4...v0.16.5
v0.16.4Compare Source
What's Changed
*types.Aliaswith Go 1.23 by @mtardy in https://github.com/kubernetes-sigs/controller-tools/pull/1061Dependencies
New Contributors
Full Changelog: kubernetes-sigs/controller-tools@v0.16.3...v0.16.4
v0.16.3Compare Source
Published binaries on previous v0.16.x releases were reporting an incorrect version.
What's Changed
Dependencies
New Contributors
Full Changelog: kubernetes-sigs/controller-tools@v0.16.2...v0.16.3
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.