-
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(go.mod/go.sum): update minor dependencies (golang) #7
Conversation
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
2e49c40
to
0277487
Compare
c302a5f
to
eefafcf
Compare
e32b825
to
e238956
Compare
dcda08c
to
d72413c
Compare
d72413c
to
acb7220
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. |
This PR contains the following updates:
v1.1.1
->v1.2.0
v3.8.1
->v3.9.0
v0.30.2
->v0.31.0
v0.30.2
->v0.31.0
v0.30.2
->v0.31.0
v0.30.2
->v0.31.0
v0.18.4
->v0.19.0
Release Notes
FiloSottile/age (filippo.io/age)
v1.2.0
: age v1.2.0Compare Source
A small release to build the release binaries with a more recent Go toolchain, and to fix a couple CLI edge cases (https://github.com/FiloSottile/age/issues/491, https://github.com/FiloSottile/age/issues/555).
The Go module now exposes a plugin package that provides an age plugin client. That is, Recipient and Identity implementations that invoke a plugin binary, allowing the use of age plugins in Go programs.
Finally, Recipients can now return a set of "labels" by implementing RecipientWithLabels. This allows replicating the special behavior of the scrypt Recipient in third-party Recipients, or applying policy useful for authenticated or post-quantum Recipients.
getsops/sops (github.com/getsops/sops/v3)
v3.9.0
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.0.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.0.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.0
ghcr.io/getsops/sops:v3.9.0-alpine
Quay.io
quay.io/getsops/sops:v3.9.0
quay.io/getsops/sops:v3.9.0-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
--filename
is used, use the provided filename without random suffix by @felixfontein in https://github.com/getsops/sops/pull/1474merge
key for key groups and make keys unique by @jonasbadstuebner in https://github.com/getsops/sops/pull/1493New Contributors
Full Changelog: getsops/sops@v3.8.1...v3.9.0
kubernetes/apiextensions-apiserver (k8s.io/apiextensions-apiserver)
v0.31.0
Compare Source
v0.30.4
Compare Source
v0.30.3
Compare Source
kubernetes/apimachinery (k8s.io/apimachinery)
v0.31.0
Compare Source
v0.30.4
Compare Source
v0.30.3
Compare Source
kubernetes/client-go (k8s.io/client-go)
v0.31.0
Compare Source
v0.30.4
Compare Source
v0.30.3
Compare Source
kubernetes/kube-aggregator (k8s.io/kube-aggregator)
v0.31.0
Compare Source
v0.30.4
Compare Source
v0.30.3
Compare Source
kubernetes-sigs/controller-runtime (sigs.k8s.io/controller-runtime)
v0.19.0
Compare Source
Please note that
admission.Defaulter/Validator
have been deprecated in favor ofadmission.CustomDefaulter/CustomValidator
since v0.17 and will be removed with v0.20.✨ New Features
controller
label to workqueue metrics (#2895)🐛 Bug Fixes
🌱 Others
📖 Additionally, there have been 5 contributions to our documentation. (#2830, #2849, #2863, #2894, #2899, #2910)
Dependencies
Added
Changed
a9213ee
→f3d0a9c
b75ee88
→f48c80b
e35e4cc
23370e0
→5315273
b8732ec
→f6361c8
f966b18
→b8732ec
3b25d92
→18e509b
Removed
Thanks to all our contributors! 😊
v0.18.5
Compare Source
What's Changed
Full Changelog: kubernetes-sigs/controller-runtime@v0.18.4...v0.18.5
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.