fix(deps): update module github.com/getsops/sops/v3 to v3.13.3 - #580
Open
renovate[bot] wants to merge 1 commit into
Open
fix(deps): update module github.com/getsops/sops/v3 to v3.13.3#580renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
Contributor
Author
ℹ️ 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/github.com-getsops-sops-v3-3.x
branch
3 times, most recently
from
March 6, 2026 10:44
4dcdeb1 to
7522d8a
Compare
renovate
Bot
force-pushed
the
renovate/github.com-getsops-sops-v3-3.x
branch
3 times, most recently
from
March 12, 2026 14:09
cc52ebf to
82a6e85
Compare
Member
|
Fails in go build with: |
marians
pushed a commit
that referenced
this pull request
Mar 13, 2026
Update github.com/getsops/sops/v3 from v3.10.2 to v3.12.1, matching the intent of PR #580. The key fix is updating the google.golang.org/grpc replace directive from v1.68.1 to v1.79.1. The old pin predated the ALTSPerRPCCreds field on DefaultCredentialsOptions (introduced in grpc v1.69.0), which cloud.google.com/go/auth v0.18.1 requires. This caused the build failure: "defaultCredetialsOptions.ALTSPerRPCCreds undefined". Also bumps transitive cloud/Azure/AWS SDK dependencies to versions required by sops v3.12.1. CI will run go mod tidy to finalize the full dependency tree. https://claude.ai/code/session_01RM8B2oD1SAesn2yqPEdRW7
renovate
Bot
force-pushed
the
renovate/github.com-getsops-sops-v3-3.x
branch
from
March 13, 2026 10:51
82a6e85 to
e9ec48a
Compare
renovate
Bot
force-pushed
the
renovate/github.com-getsops-sops-v3-3.x
branch
3 times, most recently
from
March 24, 2026 07:16
5e9f8d4 to
022d47f
Compare
renovate
Bot
force-pushed
the
renovate/github.com-getsops-sops-v3-3.x
branch
2 times, most recently
from
March 30, 2026 09:46
8b47493 to
bd58d8c
Compare
renovate
Bot
force-pushed
the
renovate/github.com-getsops-sops-v3-3.x
branch
3 times, most recently
from
April 10, 2026 10:40
7f3192a to
d9faaeb
Compare
renovate
Bot
force-pushed
the
renovate/github.com-getsops-sops-v3-3.x
branch
from
May 10, 2026 16:07
d9faaeb to
88eabdf
Compare
renovate
Bot
force-pushed
the
renovate/github.com-getsops-sops-v3-3.x
branch
2 times, most recently
from
May 20, 2026 09:39
ba8481a to
f478bca
Compare
renovate
Bot
force-pushed
the
renovate/github.com-getsops-sops-v3-3.x
branch
2 times, most recently
from
June 4, 2026 09:37
ee5a36c to
9e5df21
Compare
renovate
Bot
force-pushed
the
renovate/github.com-getsops-sops-v3-3.x
branch
from
June 22, 2026 08:09
9e5df21 to
827a851
Compare
renovate
Bot
force-pushed
the
renovate/github.com-getsops-sops-v3-3.x
branch
4 times, most recently
from
June 26, 2026 10:10
21ff3c8 to
0464e5e
Compare
renovate
Bot
force-pushed
the
renovate/github.com-getsops-sops-v3-3.x
branch
2 times, most recently
from
June 30, 2026 17:10
81082ed to
ff800a3
Compare
renovate
Bot
force-pushed
the
renovate/github.com-getsops-sops-v3-3.x
branch
from
July 23, 2026 06:33
ff800a3 to
ec2136d
Compare
renovate
Bot
force-pushed
the
renovate/github.com-getsops-sops-v3-3.x
branch
3 times, most recently
from
August 19, 2026 08:34
0d6ba3f to
ca2c998
Compare
renovate
Bot
force-pushed
the
renovate/github.com-getsops-sops-v3-3.x
branch
3 times, most recently
from
August 21, 2026 00:30
bca1d4e to
f4a565f
Compare
renovate
Bot
force-pushed
the
renovate/github.com-getsops-sops-v3-3.x
branch
from
August 29, 2026 18:11
f4a565f to
3170f40
Compare
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 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.10.2→v3.13.3Release Notes
getsops/sops (github.com/getsops/sops/v3)
v3.13.3Compare 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.13.3.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.13.3.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.3ghcr.io/getsops/sops:v3.13.3-alpineQuay.io
quay.io/getsops/sops:v3.13.3quay.io/getsops/sops:v3.13.3-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.13.2...v3.13.3
v3.13.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.13.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.13.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.13.2ghcr.io/getsops/sops:v3.13.2-alpineQuay.io
quay.io/getsops/sops:v3.13.2quay.io/getsops/sops:v3.13.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
go get -t -u ./...by @felixfontein in #2231New Contributors
Full Changelog: getsops/sops@v3.13.1...v3.13.2
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 the binary using the checksums file sha256sum -c sops-v3.13.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.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: getsops/sops@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 the binary using the checksums file sha256sum -c sops-v3.13.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.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: getsops/sops@v3.12.2...v3.13.0
v3.12.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.12.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.12.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.12.2ghcr.io/getsops/sops:v3.12.2-alpineQuay.io
quay.io/getsops/sops:v3.12.2quay.io/getsops/sops:v3.12.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.12.1...v3.12.2
v3.12.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.12.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.12.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.12.1ghcr.io/getsops/sops:v3.12.1-alpineQuay.io
quay.io/getsops/sops:v3.12.1quay.io/getsops/sops:v3.12.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.11.0...v3.12.1
v3.12.0Compare Source
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
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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 was generated by Mend Renovate. View the repository job log.