This repository was archived by the owner on Oct 12, 2025. It is now read-only.
Open
Conversation
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/mozilla-sops-3.x
branch
from
4ae156f to
f9fc14b
Compare
renovate
bot
force-pushed
the
renovate/mozilla-sops-3.x
branch
from
f9fc14b to
fc3ccb4
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/mozilla-sops-3.x
branch
from
fc3ccb4 to
81ee3c5
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/mozilla-sops-3.x
branch
from
81ee3c5 to
1ab0119
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/mozilla-sops-3.x
branch
from
1ab0119 to
37a3560
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/mozilla-sops-3.x
branch
from
37a3560 to
fb94286
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/mozilla-sops-3.x
branch
from
fb94286 to
49482e5
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/mozilla-sops-3.x
branch
from
49482e5 to
42066e8
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/mozilla-sops-3.x
branch
from
42066e8 to
fcbb27d
Compare
renovate
bot
changed the title
Signed-off-by: Zoltán Horváth <zhorvath83@users.noreply.github.com>
renovate
bot
force-pushed
the
renovate/mozilla-sops-3.x
branch
from
fcbb27d to
b7a7f97
Compare
renovate
bot
changed the title
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.7.3->v3.11.0Release Notes
mozilla/sops (mozilla/sops)
v3.11.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 the binary using the checksums file sha256sum -c sops-v3.11.0.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.11.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.11.0ghcr.io/getsops/sops:v3.11.0-alpineQuay.io
quay.io/getsops/sops:v3.11.0quay.io/getsops/sops:v3.11.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
--value-stdinoption tosops setby @felixfontein in getsops#1894New Contributors
Full Changelog: getsops/sops@v3.10.2...v3.11.0
v3.10.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.10.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.10.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.10.2ghcr.io/getsops/sops:v3.10.2-alpineQuay.io
quay.io/getsops/sops:v3.10.2quay.io/getsops/sops:v3.10.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
LoadPlainFile()by @felixfontein in getsops#1829Full Changelog: getsops/sops@v3.10.1...v3.10.2
v3.10.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.10.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.10.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.10.1ghcr.io/getsops/sops:v3.10.1-alpineQuay.io
quay.io/getsops/sops:v3.10.1quay.io/getsops/sops:v3.10.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: getsops/sops@v3.10.0...v3.10.1
v3.10.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 the binary using the checksums file sha256sum -c sops-v3.10.0.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.10.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.10.0ghcr.io/getsops/sops:v3.10.0-alpineQuay.io
quay.io/getsops/sops:v3.10.0quay.io/getsops/sops:v3.10.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
oauth2.TokenSourcein GCP KMS by @matheuscscp in getsops#1794GOOGLE_OAUTH_ACCESS_TOKENfor Google Cloud Platform by @marensofier in getsops#1578.sops.ymlfiles found while searching for.sops.yamlby @felixfontein in getsops#1820New Contributors
Full Changelog: getsops/sops@v3.9.4...v3.10.0
v3.9.4Compare 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.4.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.4.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.4ghcr.io/getsops/sops:v3.9.4-alpineQuay.io
quay.io/getsops/sops:v3.9.4quay.io/getsops/sops:v3.9.4-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: getsops/sops@v3.9.3...v3.9.4
v3.9.3[Compare
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.