-
Notifications
You must be signed in to change notification settings - Fork 0
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
fix(deps): update non-minor dependencies #27
base: main
Are you sure you want to change the base?
Conversation
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
69cf11c
to
5184f48
Compare
4085852
to
c64971c
Compare
|
0b4d935
to
40336be
Compare
490294f
to
b77571e
Compare
10ea0fc
to
c253c32
Compare
c253c32
to
e155fea
Compare
This PR contains the following updates:
v3.9.2
->v3.9.3
v0.3.59
->v0.3.64
v0.2.21
->v0.2.24
1.23.4
->1.23.5
1.23.4
->1.23.5
v0.32.0
->v0.32.1
v0.32.0
->v0.32.1
v0.32.0
->v0.32.1
v0.32.0
->v0.32.1
v0.32.0
->v0.32.1
aea2e32
->aafb269
Release Notes
getsops/sops (github.com/getsops/sops/v3)
v3.9.3
Compare 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.3.checksums.txt --ignore-missing
Verify 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.3.intoto.jsonl
. To verify the provenance of an artifact, you can utilize theslsa-verifier
tool:Container Images
The
sops
binaries 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/amd64
andlinux/arm64
.GitHub Container Registry
ghcr.io/getsops/sops:v3.9.3
ghcr.io/getsops/sops:v3.9.3-alpine
Quay.io
quay.io/getsops/sops:v3.9.3
quay.io/getsops/sops:v3.9.3-alpine
Verify 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-verifier
documentation.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
Full Changelog: getsops/sops@v3.9.2...v3.9.3
sap/component-operator-runtime (github.com/sap/component-operator-runtime)
v0.3.64
Compare Source
v0.3.63
Compare Source
v0.3.62
Compare Source
Incompatible changes
Previously, the forced re-apply of dependent objects was based on a timestamp that was coded into the object digest. As a consequence, the digest annotation of every dependent object was updated more or less every 60 minutes. Which caused problems (e.g. with crossplane).
From this release onwards, the force-re-apply mechanism is based on the new status field
status.inventory[].lastAppliedAt
.Note: YOU MUST, REALLY MUST, regenerate your component CRD when using a version of component-operator-runtime containing this release, and ship the module update together with the updated CRD!!!
v0.3.61
Compare Source
v0.3.60
Compare Source
sap/go-generics (github.com/sap/go-generics)
v0.2.24
Compare Source
v0.2.23
Compare Source
v0.2.22
Compare Source
golang/go (go)
v1.23.5
kubernetes/apiextensions-apiserver (k8s.io/apiextensions-apiserver)
v0.32.1
Compare Source
kubernetes/apimachinery (k8s.io/apimachinery)
v0.32.1
Compare Source
kubernetes/client-go (k8s.io/client-go)
v0.32.1
Compare Source
kubernetes/code-generator (k8s.io/code-generator)
v0.32.1
Compare Source
kubernetes/kube-aggregator (k8s.io/kube-aggregator)
v0.32.1
Compare Source
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.