chore(deps): update dependency getsops/sops to v3.13.1 #4
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "renovate/getsops-sops-3.13.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
v3.12.2→v3.13.1Release Notes
getsops/sops (getsops/sops)
v3.13.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 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.13.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.13.1ghcr.io/getsops/sops:v3.13.1-alpineQuay.io
quay.io/getsops/sops:v3.13.1quay.io/getsops/sops:v3.13.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
Full Changelog: https://github.com/getsops/sops/compare/v3.13.0...v3.13.1
v3.13.0Compare 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 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.13.0.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.13.0ghcr.io/getsops/sops:v3.13.0-alpineQuay.io
quay.io/getsops/sops:v3.13.0quay.io/getsops/sops:v3.13.0-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
--filenameby @felixfontein in #2155--indentglobal flag value and pass it to store configs by @skirino in #2156New Contributors
Full Changelog: https://github.com/getsops/sops/compare/v3.12.2...v3.13.0
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate.
7a85da38cato83046b0a1cchore(deps): update dependency getsops/sops to v3.13.0to chore(deps): update dependency getsops/sops to v3.13.1