Skip to content

Redirect documentation to github.com/getsops/docs/#2083

Merged
felixfontein merged 4 commits into
getsops:mainfrom
felixfontein:docs-branching
May 15, 2026
Merged

Redirect documentation to github.com/getsops/docs/#2083
felixfontein merged 4 commits into
getsops:mainfrom
felixfontein:docs-branching

Conversation

@felixfontein
Copy link
Copy Markdown
Contributor

Related: getsops/docs#25

@sabre1041
Copy link
Copy Markdown
Contributor

@felixfontein this looks good. Do you want to remove the draft designation and make it ready for review?

@felixfontein felixfontein marked this pull request as ready for review May 11, 2026 04:33
@felixfontein
Copy link
Copy Markdown
Contributor Author

I removed the draft state, but the PR has been ready for review since February. The draft state has only been there to prevent premature merging, since this PR, the other PR, creating the branches, and doing the netlify setup needs to be done at the same time.

Signed-off-by: Felix Fontein <felix@fontein.de>
Signed-off-by: Felix Fontein <felix@fontein.de>
Signed-off-by: Felix Fontein <felix@fontein.de>
Signed-off-by: Felix Fontein <felix@fontein.de>
Copy link
Copy Markdown
Contributor

@sabre1041 sabre1041 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@felixfontein felixfontein merged commit dbb597b into getsops:main May 15, 2026
14 checks passed
@felixfontein felixfontein deleted the docs-branching branch May 15, 2026 14:17
tmeijn pushed a commit to tmeijn/dotfiles that referenced this pull request May 18, 2026
This MR contains the following updates:

| Package | Update | Change |
|---|---|---|
| [getsops/sops](https://github.com/getsops/sops) | patch | `v3.13.0` → `v3.13.1` |

MR created with the help of [el-capitano/tools/renovate-bot](https://gitlab.com/el-capitano/tools/renovate-bot).

**Proposed changes to behavior should be submitted there as MRs.**

---

### Release Notes

<details>
<summary>getsops/sops (getsops/sops)</summary>

### [`v3.13.1`](https://github.com/getsops/sops/releases/tag/v3.13.1)

[Compare Source](getsops/sops@v3.13.0...v3.13.1)

#### 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:

```shell

# 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](https://docs.sigstore.dev/cosign/overview/) with GitHub OIDC. To validate the signature of this file, run the following commands:

```shell

# 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:

```shell

# Verify the binary using the checksums file
sha256sum -c sops-v3.13.1.checksums.txt --ignore-missing
```

##### Verify artifact provenance

The [SLSA provenance](https://slsa.dev/provenance/v0.2) of the binaries, packages, and SBOMs can be found within the artifacts associated with this release. It is presented through an [in-toto](https://in-toto.io/) link metadata file named `sops-v3.13.1.intoto.jsonl`. To verify the provenance of an artifact, you can utilize the [`slsa-verifier`](https://github.com/slsa-framework/slsa-verifier#artifacts) tool:

```shell

# 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](https://docs.sigstore.dev/cosign/overview/) with GitHub OIDC. To validate the signature of an image, run the following command:

```shell
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](https://slsa.dev/provenance/v0.2) attestations. For more information around the verification of this, please refer to the [`slsa-verifier` documentation](https://github.com/slsa-framework/slsa-verifier#containers).

#### 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](https://spdx.dev/) JSON file, formatted as `<binary>.spdx.sbom.json`.

#### What's Changed

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

**Full Changelog**: <getsops/sops@v3.13.0...v3.13.1>

</details>

---

### Configuration

📅 **Schedule**: (UTC)

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

🚦 **Automerge**: Enabled.

♻ **Rebasing**: Whenever MR is behind base branch, or you tick the rebase/retry checkbox.

🔕 **Ignore**: Close this MR and you won't be reminded about this update again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this MR, check this box

---

This MR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4xODAuMCIsInVwZGF0ZWRJblZlciI6IjQzLjE4MC4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJSZW5vdmF0ZSBCb3QiLCJhdXRvbWF0aW9uOmJvdC1hdXRob3JlZCIsImRlcGVuZGVuY3ktdHlwZTo6cGF0Y2giXX0=-->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants