chore(deps): update ghcr.io/getsops/sops docker tag to v3.13.3 by doyobot[bot] · Pull Request #140 · kilip/containers

doyobot · 2026-05-08T18:13:04Z

This PR contains the following updates:

Package	Type	Update	Change
ghcr.io/getsops/sops	stage	minor	`v3.12.2-alpine` → `v3.13.3-alpine`

Release Notes

getsops/sops (ghcr.io/getsops/sops)

`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

Add ini to supported input/output type descriptions by @TheKhanj in #2239
build(deps): Bump the go group with 10 updates by @dependabot[bot] in #2242
build(deps): Bump the ci group with 6 updates by @dependabot[bot] in #2241
fix: include decrypted sequence comments in the MAC (fixes #2243) by @cbcoutinho in #2245
build(deps): Bump the go group with 14 updates by @dependabot[bot] in #2251
build(deps): Bump the ci group with 2 updates by @dependabot[bot] in #2250
build(deps): Bump the go group with 11 updates by @dependabot[bot] in #2261
build(deps): Bump the ci group with 3 updates by @dependabot[bot] in #2260
build(deps): Bump the rust group in /functional-tests with 3 updates by @dependabot[bot] in #2259
Update dependencies with 'go get -t -u ./...' by @felixfontein in #2248
Completion scripts: remove leading newline by @felixfontein in #2253
Release 3.13.3 by @felixfontein in #2249

New Contributors

@TheKhanj made their first contribution in #2239
@cbcoutinho made their first contribution in #2245

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

build(deps): Bump the go group with 3 updates by @dependabot[bot] in #2185
build(deps): Bump github/codeql-action from 4.35.4 to 4.35.5 in the ci group by @dependabot[bot] in #2184
build(deps): Bump the go group with 11 updates by @dependabot[bot] in #2193
build(deps): Bump the ci group with 4 updates by @dependabot[bot] in #2192
build(deps): Bump serde_json from 1.0.149 to 1.0.150 in /functional-tests in the rust group by @dependabot[bot] in #2191
build(deps): Bump the go group with 11 updates by @dependabot[bot] in #2197
build(deps): Bump docker/setup-qemu-action from 4.0.0 to 4.1.0 in the ci group by @dependabot[bot] in #2196
test: unset all age env vars in make test target by @arpitjain099 in #2208
build(deps): Bump the go group with 10 updates by @dependabot[bot] in #2212
build(deps): Bump the ci group with 2 updates by @dependabot[bot] in #2211
build(deps): Bump the go group with 15 updates by @dependabot[bot] in #2218
build(deps): Bump alpine from 3.23 to 3.24 in /.release in the docker group by @dependabot[bot] in #2217
fix: handle pointers when serializing context by @tlercher in #2219
docs: fix typo in exec-file --filename help text by @s3onghyun in #2221
JSON store: preserve large integers that fit into int64 by @s3onghyun in #2222
Fix panic when expecting an encrypted string, but a non-string is encountered by @felixfontein in #2227
Fix INI store no longer double-encoding newlines by @felixfontein in #2189
exec-file/exec-env: reset supplementary groups when changing user by @felixfontein in #2194
build(deps): Bump the go group with 6 updates by @dependabot[bot] in #2229
build(deps): Bump actions/checkout from 6.0.3 to 7.0.0 in the ci group by @dependabot[bot] in #2228
Fix issue when changing user in exec subcommands by @sabre1041 in #2230
Shorten .md lines by @felixfontein in #2206
Update all Go dependencies with go get -t -u ./... by @felixfontein in #2231
build(deps): Bump github.com/opencontainers/runc from 1.2.8 to 1.3.6 by @dependabot[bot] in #2233
build(deps): Bump the ci group with 2 updates by @dependabot[bot] in #2236
Release 3.13.2 by @felixfontein in #2232

New Contributors

@arpitjain099 made their first contribution in #2208
@tlercher made their first contribution in #2219
@s3onghyun made their first contribution in #2221

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

build(deps): Bump the go group with 9 updates by @dependabot[bot] in #2178
build(deps): Bump the ci group with 2 updates by @dependabot[bot] in #2177
Apply 'gofmt -w -s' to all .go files by @felixfontein in #2181
GPG agent for age key passwords: avoid percent-encoding of cache key to blow up size > 50 characters by @felixfontein in #2180
Redirect documentation to github.com/getsops/docs/ by @felixfontein in #2083
Release 3.13.1 by @felixfontein in #2183

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

build(deps): Bump google.golang.org/grpc from 1.79.1 to 1.79.3 by @dependabot[bot] in #2110
build(deps): Bump the ci group with 3 updates by @dependabot[bot] in #2117
build(deps): Bump the ci group with 3 updates by @dependabot[bot] in #2126
build(deps): Bump github.com/go-jose/go-jose/v4 from 4.1.3 to 4.1.4 by @dependabot[bot] in #2133
build(deps): Bump docker/login-action from 4.0.0 to 4.1.0 in the ci group by @dependabot[bot] in #2139
Improve error message for top-level arrays by @kushal9897 in #2138
build(deps): Bump github.com/aws/aws-sdk-go-v2/service/s3 from 1.96.0 to 1.97.3 by @dependabot[bot] in #2142
docs: add get key permission requirement for Azure Key Vault when version is omitted by @Hanashiko in #2122
build(deps): Bump actions/upload-artifact from 7.0.0 to 7.0.1 in the ci group by @dependabot[bot] in #2149
Use prefixed and truncated key hash instead of location as GPG agent cache key by @felixfontein in #2145
Drop support for Go 1.24 by @felixfontein in #2141
build(deps): Bump go.opentelemetry.io/otel/sdk from 1.40.0 to 1.43.0 by @dependabot[bot] in #2146
build(deps): Bump the go group across 1 directory with 21 updates by @dependabot[bot] in #2144
Add SOPS_GCP_KMS_ENDPOINT and SOPS_GCP_KMS_UNIVERSE_DOMAIN env vars by @DnR-iData in #2114
Preserve YAML inline comments through encrypt/edit roundtrip by @knowald in #2131
Update release for cosign v3 by @sabre1041 in #2082
build(deps): Bump the ci group with 3 updates by @dependabot[bot] in #2151
build(deps): Bump the go group with 12 updates by @dependabot[bot] in #2152
Update broken link in README by @manute in #2153
sops exec-file: make sure to set GID to correct value instead of UID by @felixfontein in #2154
sops exec-file: improve error handling, reject non-local paths in --filename by @felixfontein in #2155
Obtain --indent global flag value and pass it to store configs by @skirino in #2156
build(deps): Bump the go group with 3 updates by @dependabot[bot] in #2159
build(deps): Bump goreleaser/goreleaser-action from 7.1.0 to 7.2.1 in the ci group by @dependabot[bot] in #2158
Update all Go dependencies with 'go get -t -u ./...' by @felixfontein in #2165
Allow to have space-separated keys in SOPS_AGE_KEY by @felixfontein in #2086
HC Vault: add allowlist support for acceptable HC Vault URLs by @felixfontein in #2164
build(deps): Bump the go group with 5 updates by @dependabot[bot] in #2171
build(deps): Bump github/codeql-action from 4.35.2 to 4.35.3 in the ci group by @dependabot[bot] in #2173
Use mapstructure to (de-)serialize internal metadata; move metadata processing from specific stores to general place by @felixfontein in #2120
Release 3.13.0 by @felixfontein in #2176

New Contributors

@kushal9897 made their first contribution in #2138
@Hanashiko made their first contribution in #2122
@DnR-iData made their first contribution in #2114
@knowald made their first contribution in #2131
@manute made their first contribution in #2153
@skirino made their first contribution in #2156

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

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 has been generated by Mend Renovate CLI.

| datasource | package | from | to | | ---------- | -------------------- | ------- | ------- | | docker | ghcr.io/getsops/sops | v3.12.2 | v3.13.3 |

doyobot Bot requested a review from kilip as a code owner May 8, 2026 18:13

doyobot Bot force-pushed the renovate/ghcr.io-getsops-sops-3.x branch 2 times, most recently from 6c982ad to e63bf82 Compare May 16, 2026 15:00

doyobot Bot changed the title ~~chore(deps): update ghcr.io/getsops/sops docker tag to v3.13.0~~ chore(deps): update ghcr.io/getsops/sops docker tag to v3.13.1 May 16, 2026

doyobot Bot force-pushed the renovate/ghcr.io-getsops-sops-3.x branch from e63bf82 to d7fc222 Compare June 8, 2026 05:55

doyobot Bot force-pushed the renovate/ghcr.io-getsops-sops-3.x branch 2 times, most recently from 1452706 to c33b3f0 Compare June 29, 2026 04:24

doyobot Bot force-pushed the renovate/ghcr.io-getsops-sops-3.x branch from c33b3f0 to 4ba1ee7 Compare June 30, 2026 09:49

doyobot Bot changed the title ~~chore(deps): update ghcr.io/getsops/sops docker tag to v3.13.1~~ chore(deps): update ghcr.io/getsops/sops docker tag to v3.13.2 Jun 30, 2026

doyobot Bot force-pushed the renovate/ghcr.io-getsops-sops-3.x branch 2 times, most recently from 2a485bd to 85163bb Compare July 13, 2026 04:33

doyobot Bot force-pushed the renovate/ghcr.io-getsops-sops-3.x branch 2 times, most recently from bd6dcd9 to 6de45af Compare July 23, 2026 07:35

doyobot Bot changed the title ~~chore(deps): update ghcr.io/getsops/sops docker tag to v3.13.2~~ chore(deps): update ghcr.io/getsops/sops docker tag to v3.13.3 Jul 23, 2026

doyobot Bot force-pushed the renovate/ghcr.io-getsops-sops-3.x branch 3 times, most recently from c3ee4cf to 066aad8 Compare August 3, 2026 04:34

chore(deps): update ghcr.io/getsops/sops docker tag to v3.13.3

68e237e

| datasource | package | from | to | | ---------- | -------------------- | ------- | ------- | | docker | ghcr.io/getsops/sops | v3.12.2 | v3.13.3 |

doyobot Bot force-pushed the renovate/ghcr.io-getsops-sops-3.x branch from 066aad8 to 68e237e Compare August 10, 2026 02:08

Navigation Menu

chore(deps): update ghcr.io/getsops/sops docker tag to v3.13.3 - #140

chore(deps): update ghcr.io/getsops/sops docker tag to v3.13.3#140
doyobot[bot] wants to merge 1 commit into
mainfrom
renovate/ghcr.io-getsops-sops-3.x

doyobot Bot commented May 8, 2026 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

doyobot Bot commented May 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

v3.13.3

Installation

Verify checksums file signature

Verify binary integrity

Verify artifact provenance

Container Images

GitHub Container Registry

Quay.io

Verify container image signature

Verify container image provenance

Software Bill of Materials

What's Changed

New Contributors

v3.13.2

Installation

Verify checksums file signature

Verify binary integrity

Verify artifact provenance

Container Images

GitHub Container Registry

Quay.io

Verify container image signature

Verify container image provenance

Software Bill of Materials

What's Changed

New Contributors

v3.13.1

Installation

Verify checksums file signature

Verify binary integrity

Verify artifact provenance

Container Images

GitHub Container Registry

Quay.io

Verify container image signature

Verify container image provenance

Software Bill of Materials

What's Changed

v3.13.0

Installation

Verify checksums file signature

Verify binary integrity

Verify artifact provenance

Container Images

GitHub Container Registry

Quay.io

Verify container image signature

Verify container image provenance

Software Bill of Materials

What's Changed

New Contributors

Configuration

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

doyobot Bot commented May 8, 2026 •

edited

Loading

`v3.13.3`

`v3.13.2`

`v3.13.1`

`v3.13.0`