Skip to content

fix(deps): update module github.com/getsops/sops/v3 to v3.13.3 - #580

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/github.com-getsops-sops-v3-3.x
Open

fix(deps): update module github.com/getsops/sops/v3 to v3.13.3#580
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/github.com-getsops-sops-v3-3.x

Conversation

@renovate

@renovate renovate Bot commented Feb 27, 2026

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
github.com/getsops/sops/v3 v3.10.2v3.13.3 age confidence

Release Notes

getsops/sops (github.com/getsops/sops/v3)

v3.13.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:

# Download the binary
curl -LO https://github.com/getsops/sops/releases/download/v3.13.3/sops-v3.13.3.linux.amd64

# Move the binary in to your PATH
mv sops-v3.13.3.linux.amd64 /usr/local/bin/sops

# Make the binary executable
chmod +x /usr/local/bin/sops
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:

# Download the checksums file, certificate and signature
curl -LO https://github.com/getsops/sops/releases/download/v3.13.3/sops-v3.13.3.checksums.txt
curl -LO https://github.com/getsops/sops/releases/download/v3.13.3/sops-v3.13.3.checksums.sigstore.json

# Verify the checksums file
cosign verify-blob sops-v3.13.3.checksums.txt \
  --bundle sops-v3.13.3.checksums.sigstore.json \
  --certificate-identity-regexp=https://github.com/getsops \
  --certificate-oidc-issuer=https://token.actions.githubusercontent.com
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-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.13.3.intoto.jsonl. To verify the provenance of an artifact, you can utilize the slsa-verifier tool:

# Download the metadata file
curl -LO  https://github.com/getsops/sops/releases/download/v3.13.3/sops-v3.13.3.intoto.jsonl

# Verify the provenance of the artifact
slsa-verifier verify-artifact <artifact> \
  --provenance-path sops-v3.13.3.intoto.jsonl \
  --source-uri github.com/getsops/sops \
  --source-tag v3.13.3

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 and linux/arm64.

GitHub Container Registry
  • ghcr.io/getsops/sops:v3.13.3
  • ghcr.io/getsops/sops:v3.13.3-alpine
Quay.io
  • quay.io/getsops/sops:v3.13.3
  • quay.io/getsops/sops:v3.13.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:

cosign verify ghcr.io/getsops/sops:v3.13.3 \
  --certificate-identity-regexp=https://github.com/getsops \
  --certificate-oidc-issuer=https://token.actions.githubusercontent.com \
  -o text
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

New Contributors

Full Changelog: getsops/sops@v3.13.2...v3.13.3

v3.13.2

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:

# Download the binary
curl -LO https://github.com/getsops/sops/releases/download/v3.13.2/sops-v3.13.2.linux.amd64

# Move the binary in to your PATH
mv sops-v3.13.2.linux.amd64 /usr/local/bin/sops

# Make the binary executable
chmod +x /usr/local/bin/sops
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:

# Download the checksums file, certificate and signature
curl -LO https://github.com/getsops/sops/releases/download/v3.13.2/sops-v3.13.2.checksums.txt
curl -LO https://github.com/getsops/sops/releases/download/v3.13.2/sops-v3.13.2.checksums.sigstore.json

# Verify the checksums file
cosign verify-blob sops-v3.13.2.checksums.txt \
  --bundle sops-v3.13.2.checksums.sigstore.json \
  --certificate-identity-regexp=https://github.com/getsops \
  --certificate-oidc-issuer=https://token.actions.githubusercontent.com
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-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.13.2.intoto.jsonl. To verify the provenance of an artifact, you can utilize the slsa-verifier tool:

# Download the metadata file
curl -LO  https://github.com/getsops/sops/releases/download/v3.13.2/sops-v3.13.2.intoto.jsonl

# Verify the provenance of the artifact
slsa-verifier verify-artifact <artifact> \
  --provenance-path sops-v3.13.2.intoto.jsonl \
  --source-uri github.com/getsops/sops \
  --source-tag v3.13.2

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 and linux/arm64.

GitHub Container Registry
  • ghcr.io/getsops/sops:v3.13.2
  • ghcr.io/getsops/sops:v3.13.2-alpine
Quay.io
  • quay.io/getsops/sops:v3.13.2
  • quay.io/getsops/sops:v3.13.2-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:

cosign verify ghcr.io/getsops/sops:v3.13.2 \
  --certificate-identity-regexp=https://github.com/getsops \
  --certificate-oidc-issuer=https://token.actions.githubusercontent.com \
  -o text
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

New Contributors

Full Changelog: getsops/sops@v3.13.1...v3.13.2

v3.13.1

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:

# Download the binary
curl -LO https://github.com/getsops/sops/releases/download/v3.13.1/sops-v3.13.1.linux.amd64

# Move the binary in to your PATH
mv sops-v3.13.1.linux.amd64 /usr/local/bin/sops

# Make the binary executable
chmod +x /usr/local/bin/sops
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:

# Download the checksums file, certificate and signature
curl -LO https://github.com/getsops/sops/releases/download/v3.13.1/sops-v3.13.1.checksums.txt
curl -LO https://github.com/getsops/sops/releases/download/v3.13.1/sops-v3.13.1.checksums.sigstore.json

# Verify the checksums file
cosign verify-blob sops-v3.13.1.checksums.txt \
  --bundle sops-v3.13.1.checksums.sigstore.json \
  --certificate-identity-regexp=https://github.com/getsops \
  --certificate-oidc-issuer=https://token.actions.githubusercontent.com
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-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.13.1.intoto.jsonl. To verify the provenance of an artifact, you can utilize the slsa-verifier tool:

# Download the metadata file
curl -LO  https://github.com/getsops/sops/releases/download/v3.13.1/sops-v3.13.1.intoto.jsonl

# Verify the provenance of the artifact
slsa-verifier verify-artifact <artifact> \
  --provenance-path sops-v3.13.1.intoto.jsonl \
  --source-uri github.com/getsops/sops \
  --source-tag v3.13.1

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 and linux/arm64.

GitHub Container Registry
  • ghcr.io/getsops/sops:v3.13.1
  • ghcr.io/getsops/sops:v3.13.1-alpine
Quay.io
  • quay.io/getsops/sops:v3.13.1
  • quay.io/getsops/sops:v3.13.1-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:

cosign verify ghcr.io/getsops/sops:v3.13.1 \
  --certificate-identity-regexp=https://github.com/getsops \
  --certificate-oidc-issuer=https://token.actions.githubusercontent.com \
  -o text
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.13.0...v3.13.1

v3.13.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:

# Download the binary
curl -LO https://github.com/getsops/sops/releases/download/v3.13.0/sops-v3.13.0.linux.amd64

# Move the binary in to your PATH
mv sops-v3.13.0.linux.amd64 /usr/local/bin/sops

# Make the binary executable
chmod +x /usr/local/bin/sops
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:

# Download the checksums file, certificate and signature
curl -LO https://github.com/getsops/sops/releases/download/v3.13.0/sops-v3.13.0.checksums.txt
curl -LO https://github.com/getsops/sops/releases/download/v3.13.0/sops-v3.13.0.checksums.sigstore.json

# Verify the checksums file
cosign verify-blob sops-v3.13.0.checksums.txt \
  --bundle sops-v3.13.0.checksums.sigstore.json \
  --certificate-identity-regexp=https://github.com/getsops \
  --certificate-oidc-issuer=https://token.actions.githubusercontent.com
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-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.13.0.intoto.jsonl. To verify the provenance of an artifact, you can utilize the slsa-verifier tool:

# Download the metadata file
curl -LO  https://github.com/getsops/sops/releases/download/v3.13.0/sops-v3.13.0.intoto.jsonl

# Verify the provenance of the artifact
slsa-verifier verify-artifact <artifact> \
  --provenance-path sops-v3.13.0.intoto.jsonl \
  --source-uri github.com/getsops/sops \
  --source-tag v3.13.0

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 and linux/arm64.

GitHub Container Registry
  • ghcr.io/getsops/sops:v3.13.0
  • ghcr.io/getsops/sops:v3.13.0-alpine
Quay.io
  • quay.io/getsops/sops:v3.13.0
  • quay.io/getsops/sops:v3.13.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:

cosign verify ghcr.io/getsops/sops:v3.13.0 \
  --certificate-identity-regexp=https://github.com/getsops \
  --certificate-oidc-issuer=https://token.actions.githubusercontent.com \
  -o text
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

New Contributors

Full Changelog: getsops/sops@v3.12.2...v3.13.0

v3.12.2

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:

# Download the binary
curl -LO https://github.com/getsops/sops/releases/download/v3.12.2/sops-v3.12.2.linux.amd64

# Move the binary in to your PATH
mv sops-v3.12.2.linux.amd64 /usr/local/bin/sops

# Make the binary executable
chmod +x /usr/local/bin/sops
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:

# Download the checksums file, certificate and signature
curl -LO https://github.com/getsops/sops/releases/download/v3.12.2/sops-v3.12.2.checksums.txt
curl -LO https://github.com/getsops/sops/releases/download/v3.12.2/sops-v3.12.2.checksums.pem
curl -LO https://github.com/getsops/sops/releases/download/v3.12.2/sops-v3.12.2.checksums.sig

# Verify the checksums file
cosign verify-blob sops-v3.12.2.checksums.txt \
  --certificate sops-v3.12.2.checksums.pem \
  --signature sops-v3.12.2.checksums.sig \
  --certificate-identity-regexp=https://github.com/getsops \
  --certificate-oidc-issuer=https://token.actions.githubusercontent.com
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-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.12.2.intoto.jsonl. To verify the provenance of an artifact, you can utilize the slsa-verifier tool:

# Download the metadata file
curl -LO  https://github.com/getsops/sops/releases/download/v3.12.2/sops-v3.12.2.intoto.jsonl

# Verify the provenance of the artifact
slsa-verifier verify-artifact <artifact> \
  --provenance-path sops-v3.12.2.intoto.jsonl \
  --source-uri github.com/getsops/sops \
  --source-tag v3.12.2

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 and linux/arm64.

GitHub Container Registry
  • ghcr.io/getsops/sops:v3.12.2
  • ghcr.io/getsops/sops:v3.12.2-alpine
Quay.io
  • quay.io/getsops/sops:v3.12.2
  • quay.io/getsops/sops:v3.12.2-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:

cosign verify ghcr.io/getsops/sops:v3.12.2 \
  --certificate-identity-regexp=https://github.com/getsops \
  --certificate-oidc-issuer=https://token.actions.githubusercontent.com \
  -o text
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

New Contributors

Full Changelog: getsops/sops@v3.12.1...v3.12.2

v3.12.1

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:

# Download the binary
curl -LO https://github.com/getsops/sops/releases/download/v3.12.1/sops-v3.12.1.linux.amd64

# Move the binary in to your PATH
mv sops-v3.12.1.linux.amd64 /usr/local/bin/sops

# Make the binary executable
chmod +x /usr/local/bin/sops
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:

# Download the checksums file, certificate and signature
curl -LO https://github.com/getsops/sops/releases/download/v3.12.1/sops-v3.12.1.checksums.txt
curl -LO https://github.com/getsops/sops/releases/download/v3.12.1/sops-v3.12.1.checksums.pem
curl -LO https://github.com/getsops/sops/releases/download/v3.12.1/sops-v3.12.1.checksums.sig

# Verify the checksums file
cosign verify-blob sops-v3.12.1.checksums.txt \
  --certificate sops-v3.12.1.checksums.pem \
  --signature sops-v3.12.1.checksums.sig \
  --certificate-identity-regexp=https://github.com/getsops \
  --certificate-oidc-issuer=https://token.actions.githubusercontent.com
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-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.12.1.intoto.jsonl. To verify the provenance of an artifact, you can utilize the slsa-verifier tool:

# Download the metadata file
curl -LO  https://github.com/getsops/sops/releases/download/v3.12.1/sops-v3.12.1.intoto.jsonl

# Verify the provenance of the artifact
slsa-verifier verify-artifact <artifact> \
  --provenance-path sops-v3.12.1.intoto.jsonl \
  --source-uri github.com/getsops/sops \
  --source-tag v3.12.1

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 and linux/arm64.

GitHub Container Registry
  • ghcr.io/getsops/sops:v3.12.1
  • ghcr.io/getsops/sops:v3.12.1-alpine
Quay.io
  • quay.io/getsops/sops:v3.12.1
  • quay.io/getsops/sops:v3.12.1-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:

cosign verify ghcr.io/getsops/sops:v3.12.1 \
  --certificate-identity-regexp=https://github.com/getsops \
  --certificate-oidc-issuer=https://token.actions.githubusercontent.com \
  -o text
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.11.0...v3.12.1

v3.12.0

Compare Source

v3.11.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:

# Download the binary
curl -LO https://github.com/getsops/sops/releases/download/v3.11.0/sops-v3.11.0.linux.amd64

# Move the binary in to your PATH
mv sops-v3.11.0.linux.amd64 /usr/local/bin/sops

# Make the binary executable
chmod +x /usr/local/bin/sops
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:

# Download the checksums file, certificate and signature
curl -LO https://github.com/getsops/sops/releases/download/v3.11.0/sops-v3.11.0.checksums.txt
curl -LO https://github.com/getsops/sops/releases/download/v3.11.0/sops-v3.11.0.checksums.pem
curl -LO https://github.com/getsops/sops/releases/download/v3.11.0/sops-v3.11.0.checksums.sig

# Verify the checksums file
cosign verify-blob sops-v3.11.0.checksums.txt \
  --certificate sops-v3.11.0.checksums.pem \
  --signature sops-v3.11.0.checksums.sig \
  --certificate-identity-regexp=https://github.com/getsops \
  --certificate-oidc-issuer=https://token.actions.githubusercontent.com
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-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.11.0.intoto.jsonl. To verify the provenance of an artifact, you can utilize the slsa-verifier tool:

# Download the metadata file
curl -LO  https://github.com/getsops/sops/releases/download/v3.11.0/sops-v3.11.0.intoto.jsonl

# Verify the provenance of the artifact
slsa-verifier verify-artifact <artifact> \
  --provenance-path sops-v3.11.0.intoto.jsonl \
  --source-uri github.com/getsops/sops \
  --source-tag v3.11.0

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 and linux/arm64.

GitHub Container Registry
  • ghcr.io/getsops/sops:v3.11.0
  • ghcr.io/getsops/sops:v3.11.0-alpine
Quay.io
  • quay.io/getsops/sops:v3.11.0
  • quay.io/getsops/sops:v3.11.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:

cosign verify ghcr.io/getsops/sops:v3.11.0 \
  --certificate-identity-regexp=https://github.com/getsops \
  --certificate-oidc-issuer=https://token.actions.githubusercontent.com \
  -o text
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

Note

PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot requested a review from a team as a code owner February 27, 2026 20:49
@renovate renovate Bot added dependencies Pull requests that update a dependency file renovate PR created by RenovateBot labels Feb 27, 2026
@renovate

renovate Bot commented Feb 27, 2026

Copy link
Copy Markdown
Contributor Author

ℹ️ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 81 additional dependencies were updated

Details:

Package Change
cel.dev/expr v0.25.1 -> v0.25.2
cloud.google.com/go v0.120.0 -> v0.123.0
cloud.google.com/go/auth v0.15.0 -> v0.22.0
cloud.google.com/go/compute/metadata v0.6.0 -> v0.9.0
cloud.google.com/go/iam v1.4.2 -> v1.12.0
cloud.google.com/go/kms v1.21.1 -> v1.32.0
cloud.google.com/go/longrunning v0.6.6 -> v1.2.0
cloud.google.com/go/monitoring v1.24.1 -> v1.30.0
cloud.google.com/go/storage v1.51.0 -> v1.63.1
dario.cat/mergo v1.0.1 -> v1.0.2
filippo.io/age v1.2.1 -> v1.3.1
filippo.io/edwards25519 v1.1.0 -> v1.2.0
github.com/Azure/azure-sdk-for-go/sdk/azcore v1.18.0 -> v1.22.0
github.com/Azure/azure-sdk-for-go/sdk/azidentity v1.9.0 -> v1.14.0
github.com/Azure/azure-sdk-for-go/sdk/internal v1.11.1 -> v1.12.0
github.com/Azure/azure-sdk-for-go/sdk/security/keyvault/azkeys v1.3.1 -> v1.5.0
github.com/Azure/azure-sdk-for-go/sdk/security/keyvault/internal v1.1.1 -> v1.2.0
github.com/AzureAD/microsoft-authentication-library-for-go v1.4.2 -> v1.7.2
github.com/GoogleCloudPlatform/opentelemetry-operations-go/detectors/gcp v1.27.0 -> v1.34.0
github.com/GoogleCloudPlatform/opentelemetry-operations-go/exporter/metric v0.51.0 -> v0.58.0
github.com/GoogleCloudPlatform/opentelemetry-operations-go/internal/resourcemapping v0.51.0 -> v0.58.0
github.com/ProtonMail/go-crypto v1.3.0 -> v1.4.1
github.com/aws/aws-sdk-go-v2 v1.36.3 -> v1.42.1
github.com/aws/aws-sdk-go-v2/aws/protocol/eventstream v1.6.10 -> v1.7.14
github.com/aws/aws-sdk-go-v2/config v1.29.14 -> v1.32.30
github.com/aws/aws-sdk-go-v2/credentials v1.17.67 -> v1.19.29
github.com/aws/aws-sdk-go-v2/feature/ec2/imds v1.16.30 -> v1.18.30
github.com/aws/aws-sdk-go-v2/feature/s3/manager v1.17.72 -> v1.22.34
github.com/aws/aws-sdk-go-v2/internal/configsources v1.3.34 -> v1.4.30
github.com/aws/aws-sdk-go-v2/internal/endpoints/v2 v2.6.34 -> v2.7.30
github.com/aws/aws-sdk-go-v2/internal/v4a v1.3.34 -> v1.4.31
github.com/aws/aws-sdk-go-v2/service/internal/accept-encoding v1.12.3 -> v1.13.13
github.com/aws/aws-sdk-go-v2/service/internal/checksum v1.7.0 -> v1.9.23
github.com/aws/aws-sdk-go-v2/service/internal/presigned-url v1.12.15 -> v1.13.30
github.com/aws/aws-sdk-go-v2/service/internal/s3shared v1.18.15 -> v1.19.31
github.com/aws/aws-sdk-go-v2/service/kms v1.38.3 -> v1.54.1
github.com/aws/aws-sdk-go-v2/service/s3 v1.79.2 -> v1.105.2
github.com/aws/aws-sdk-go-v2/service/sso v1.25.3 -> v1.32.1
github.com/aws/aws-sdk-go-v2/service/ssooidc v1.30.1 -> v1.37.1
github.com/aws/aws-sdk-go-v2/service/sts v1.33.19 -> v1.44.1
github.com/aws/smithy-go v1.22.3 -> v1.27.4
github.com/cloudflare/circl v1.6.1 -> v1.6.4
github.com/cncf/xds/go v0.0.0-20250326154945-ae57f3c0d45f -> v0.0.0-20260202195803-dba9d589def2
github.com/cpuguy83/go-md2man/v2 v2.0.6 -> v2.0.7
github.com/envoyproxy/protoc-gen-validate v1.2.1 -> v1.3.3
github.com/fatih/color v1.18.0 -> v1.19.0
github.com/felixge/httpsnoop v1.0.4 -> v1.1.0
github.com/go-jose/go-jose/v4 v4.1.0 -> v4.1.4
github.com/golang-jwt/jwt/v5 v5.3.0 -> v5.3.1
github.com/googleapis/enterprise-certificate-proxy v0.3.6 -> v0.3.18
github.com/googleapis/gax-go/v2 v2.14.1 -> v2.23.0
github.com/hashicorp/go-retryablehttp v0.7.7 -> v0.7.8
github.com/hashicorp/vault/api v1.20.0 -> v1.23.0
github.com/json-iterator/go v1.1.12 -> v1.1.13-0.20220915233716-71ac16282d12
github.com/lib/pq v1.10.9 -> v1.12.3
github.com/mattn/go-colorable v0.1.14 -> v0.1.15
github.com/mattn/go-isatty v0.0.20 -> v0.0.23
github.com/sirupsen/logrus v1.9.3 -> v1.9.4
github.com/urfave/cli v1.22.16 -> v1.22.17
go.opentelemetry.io/contrib/detectors/gcp v1.35.0 -> v1.44.0
go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc v0.65.0 -> v0.69.0
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp v0.65.0 -> v0.69.0
go.opentelemetry.io/otel v1.41.0 -> v1.44.0
go.opentelemetry.io/otel/metric v1.41.0 -> v1.44.0
go.opentelemetry.io/otel/sdk v1.40.0 -> v1.44.0
go.opentelemetry.io/otel/sdk/metric v1.40.0 -> v1.44.0
go.opentelemetry.io/otel/trace v1.41.0 -> v1.44.0
golang.org/x/crypto v0.50.0 -> v0.54.0
golang.org/x/net v0.56.0 -> v0.57.0
golang.org/x/oauth2 v0.34.0 -> v0.36.0
golang.org/x/sync v0.21.0 -> v0.22.0
golang.org/x/sys v0.46.0 -> v0.47.0
golang.org/x/term v0.44.0 -> v0.45.0
golang.org/x/text v0.39.0 -> v0.40.0
golang.org/x/time v0.14.0 -> v0.15.0
google.golang.org/api v0.228.0 -> v0.289.0
google.golang.org/genproto v0.0.0-20250324211829-b45e905df463 -> v0.0.0-20260720171339-e059f2f05d78
google.golang.org/genproto/googleapis/api v0.0.0-20260128011058-8636f8732409 -> v0.0.0-20260720171339-e059f2f05d78
google.golang.org/genproto/googleapis/rpc v0.0.0-20260128011058-8636f8732409 -> v0.0.0-20260720171339-e059f2f05d78
google.golang.org/grpc v1.79.3 -> v1.82.1
gopkg.in/ini.v1 v1.67.0 -> v1.67.3

@renovate
renovate Bot force-pushed the renovate/github.com-getsops-sops-v3-3.x branch 3 times, most recently from 4dcdeb1 to 7522d8a Compare March 6, 2026 10:44
@renovate
renovate Bot force-pushed the renovate/github.com-getsops-sops-v3-3.x branch 3 times, most recently from cc52ebf to 82a6e85 Compare March 12, 2026 14:09
@marians

marians commented Mar 13, 2026

Copy link
Copy Markdown
Member

Fails in go build with:

# cloud.google.com/go/auth/grpctransport
/go/pkg/mod/cloud.google.com/go/auth@v0.18.1/grpctransport/directpath.go:131:29: defaultCredetialsOptions.ALTSPerRPCCreds undefined (type "google.golang.org/grpc/credentials/google".DefaultCredentialsOptions has no field or method ALTSPerRPCCreds)

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
renovate Bot force-pushed the renovate/github.com-getsops-sops-v3-3.x branch from 82a6e85 to e9ec48a Compare March 13, 2026 10:51
@renovate renovate Bot changed the title Update module github.com/getsops/sops/v3 to v3.12.1 Update module github.com/getsops/sops/v3 to v3.12.2 Mar 18, 2026
@renovate
renovate Bot force-pushed the renovate/github.com-getsops-sops-v3-3.x branch 3 times, most recently from 5e9f8d4 to 022d47f Compare March 24, 2026 07:16
@renovate
renovate Bot force-pushed the renovate/github.com-getsops-sops-v3-3.x branch 2 times, most recently from 8b47493 to bd58d8c Compare March 30, 2026 09:46
@renovate
renovate Bot force-pushed the renovate/github.com-getsops-sops-v3-3.x branch 3 times, most recently from 7f3192a to d9faaeb Compare April 10, 2026 10:40
@renovate
renovate Bot force-pushed the renovate/github.com-getsops-sops-v3-3.x branch from d9faaeb to 88eabdf Compare May 10, 2026 16:07
@renovate renovate Bot changed the title Update module github.com/getsops/sops/v3 to v3.12.2 fix(deps): update module github.com/getsops/sops/v3 to v3.13.0 May 10, 2026
@renovate renovate Bot changed the title fix(deps): update module github.com/getsops/sops/v3 to v3.13.0 fix(deps): update module github.com/getsops/sops/v3 to v3.13.1 May 16, 2026
@renovate
renovate Bot force-pushed the renovate/github.com-getsops-sops-v3-3.x branch 2 times, most recently from ba8481a to f478bca Compare May 20, 2026 09:39
@renovate
renovate Bot force-pushed the renovate/github.com-getsops-sops-v3-3.x branch 2 times, most recently from ee5a36c to 9e5df21 Compare June 4, 2026 09:37
@renovate
renovate Bot force-pushed the renovate/github.com-getsops-sops-v3-3.x branch from 9e5df21 to 827a851 Compare June 22, 2026 08:09
@renovate
renovate Bot force-pushed the renovate/github.com-getsops-sops-v3-3.x branch 4 times, most recently from 21ff3c8 to 0464e5e Compare June 26, 2026 10:10
@renovate renovate Bot changed the title fix(deps): update module github.com/getsops/sops/v3 to v3.13.1 fix(deps): update module github.com/getsops/sops/v3 to v3.13.2 Jun 30, 2026
@renovate
renovate Bot force-pushed the renovate/github.com-getsops-sops-v3-3.x branch 2 times, most recently from 81082ed to ff800a3 Compare June 30, 2026 17:10
@renovate
renovate Bot force-pushed the renovate/github.com-getsops-sops-v3-3.x branch from ff800a3 to ec2136d Compare July 23, 2026 06:33
@renovate renovate Bot changed the title fix(deps): update module github.com/getsops/sops/v3 to v3.13.2 fix(deps): update module github.com/getsops/sops/v3 to v3.13.3 Jul 23, 2026
@renovate
renovate Bot force-pushed the renovate/github.com-getsops-sops-v3-3.x branch 3 times, most recently from 0d6ba3f to ca2c998 Compare August 19, 2026 08:34
@renovate
renovate Bot force-pushed the renovate/github.com-getsops-sops-v3-3.x branch 3 times, most recently from bca1d4e to f4a565f Compare August 21, 2026 00:30
@renovate renovate Bot changed the title fix(deps): update module github.com/getsops/sops/v3 to v3.13.3 fix(deps): update module github.com/getsops/sops/v3 to v3.13.3 - autoclosed Aug 29, 2026
@renovate renovate Bot closed this Aug 29, 2026
@renovate
renovate Bot deleted the renovate/github.com-getsops-sops-v3-3.x branch August 29, 2026 12:56
@renovate renovate Bot changed the title fix(deps): update module github.com/getsops/sops/v3 to v3.13.3 - autoclosed fix(deps): update module github.com/getsops/sops/v3 to v3.13.3 Aug 29, 2026
@renovate renovate Bot reopened this Aug 29, 2026
@renovate
renovate Bot force-pushed the renovate/github.com-getsops-sops-v3-3.x branch from f4a565f to 3170f40 Compare August 29, 2026 18:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file renovate PR created by RenovateBot

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant