Secrets OPerationS 이전 버전 및 전체 버전

## 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.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](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.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:

```shell
# Verify the binary using the checksums file
sha256sum -c sops-v3.13.3.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.3.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.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](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.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](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
* Add ini to supporte

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 

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
- CI: Rearrange steps; disable setup-go's caching by @felixfontein in #2081
- build(deps): Bump the go group with 6 updates by @dependabot[bot] in #2085
- build(deps): Bump the ci group with 2 updates by @dependabot[bot] in #2084
- build(deps): Bump github.com/cloudflare/circl from 1.6.1 to 1.6.3 by @dependabot[bot] in #2087
- build(deps): Bump go.opentelemetry.io/otel/sdk from 1.3

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
- build(deps): Bump the go group with 4 updates by @dependabot[bot] in #1845
- build(deps): Bump the go group with 5 updates by @dependabot[bot] in #1850
- build(deps): Bump the ci group with 4 updates by @dependabot[bot] in #1849
- build(deps): Bump the go group with 8 updates by @dependabot[bot] in #1854
- build(deps): Bump tempfile from 3.19.1 to 3.20.0 in /functional-tests in t

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.10.2/sops-v3.10.2.linux.amd64
# Move the binary in to your PATH
mv sops-v3.10.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.10.2/sops-v3.10.2.checksums.txt
curl -LO https://github.com/getsops/sops/releases/download/v3.10.2/sops-v3.10.2.checksums.pem
curl -LO https://github.com/getsops/sops/releases/download/v3.10.2/sops-v3.10.2.checksums.sig
# Verify the checksums file
cosign verify-blob sops-v3.10.2.checksums.txt \
--certificate sops-v3.10.2.checksums.pem \
--signature sops-v3.10.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.10.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.10.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.10.2/sops-v3.10.2.intoto.jsonl
# Verify the provenance of the artifact
slsa-verifier verify-artifact <artifact> \
--provenance-path sops-v3.10.2.intoto.jsonl \
--source-uri github.com/getsops/sops \
--source-tag v3.10.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.10.2
- ghcr.io/getsops/sops:v3.10.2-alpine
Quay.io
- quay.io/getsops/sops:v3.10.2
- quay.io/getsops/sops:v3.10.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.10.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 13 updates by @dependabot in #1834
- Use latest 1.24 Go version for release build by @hiddeco in #1836
- Remove reserved keyword check from YAML store's LoadPlainFile() by @felixfontein in #1829
- build(deps): Bump the go group with 9 updates by @dependabot in #1839
- build(deps): Bump github/codeql-action from 3.28.13 to 3.28.15 in the ci grou

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.10.1/sops-v3.10.1.linux.amd64
# Move the binary in to your PATH
mv sops-v3.10.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.10.1/sops-v3.10.1.checksums.txt
curl -LO https://github.com/getsops/sops/releases/download/v3.10.1/sops-v3.10.1.checksums.pem
curl -LO https://github.com/getsops/sops/releases/download/v3.10.1/sops-v3.10.1.checksums.sig
# Verify the checksums file
cosign verify-blob sops-v3.10.1.checksums.txt \
--certificate sops-v3.10.1.checksums.pem \
--signature sops-v3.10.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.10.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.10.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.10.1/sops-v3.10.1.intoto.jsonl
# Verify the provenance of the artifact
slsa-verifier verify-artifact <artifact> \
--provenance-path sops-v3.10.1.intoto.jsonl \
--source-uri github.com/getsops/sops \
--source-tag v3.10.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.10.1
- ghcr.io/getsops/sops:v3.10.1-alpine
Quay.io
- quay.io/getsops/sops:v3.10.1
- quay.io/getsops/sops:v3.10.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.10.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 ci group with 2 updates by @dependabot in #1826
- Release 3.10.1 by @felixfontein in #1827
Full Changelog: v3.10.0...v3.10.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:
# Download the binary
curl -LO https://github.com/getsops/sops/releases/download/v3.10.0/sops-v3.10.0.linux.amd64
# Move the binary in to your PATH
mv sops-v3.10.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.10.0/sops-v3.10.0.checksums.txt
curl -LO https://github.com/getsops/sops/releases/download/v3.10.0/sops-v3.10.0.checksums.pem
curl -LO https://github.com/getsops/sops/releases/download/v3.10.0/sops-v3.10.0.checksums.sig
# Verify the checksums file
cosign verify-blob sops-v3.10.0.checksums.txt \
--certificate sops-v3.10.0.checksums.pem \
--signature sops-v3.10.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.10.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.10.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.10.0/sops-v3.10.0.intoto.jsonl
# Verify the provenance of the artifact
slsa-verifier verify-artifact <artifact> \
--provenance-path sops-v3.10.0.intoto.jsonl \
--source-uri github.com/getsops/sops \
--source-tag v3.10.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.10.0
- ghcr.io/getsops/sops:v3.10.0-alpine
Quay.io
- quay.io/getsops/sops:v3.10.0
- quay.io/getsops/sops:v3.10.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.10.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 alpine from 3.18 to 3.21 in /.release in the docker group across 1 directory by @dependabot in #1700
- Convert changelog to MarkDown by @felixfontein in #1741
- build(deps): Bump the go group with 7 updates by @dependabot in #1743
- build(deps): Bump the go group with 9 updates by @dependabot in #1745
- build(deps): Bump the rust group in /functional-tests with 

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.9.4/sops-v3.9.4.linux.amd64

# Move the binary in to your PATH
mv sops-v3.9.4.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.9.4/sops-v3.9.4.checksums.txt
curl -LO https://github.com/getsops/sops/releases/download/v3.9.4/sops-v3.9.4.checksums.pem
curl -LO https://github.com/getsops/sops/releases/download/v3.9.4/sops-v3.9.4.checksums.sig

# Verify the checksums file
cosign verify-blob sops-v3.9.4.checksums.txt \
--certificate sops-v3.9.4.checksums.pem \
--signature sops-v3.9.4.checksums.sig \
--certificate-identity-regexp= \
--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.9.4.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.9.4.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.9.4/sops-v3.9.4.intoto.jsonl

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

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.9.4
- ghcr.io/getsops/sops:v3.9.4-alpine
Quay.io
- quay.io/getsops/sops:v3.9.4
- quay.io/getsops/sops:v3.9.4-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.9.4 \
--certificate-identity-regexp= \
--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 5 updates by @dependabot in #1727
- build(deps): Bump tempfile from 3.14.0 to 3.15.0 in /functional-tests in the rust group by @dependabot in #1728
- build(deps): Bump the go group with 16 updates by @dependabot in #1732
- build(deps): Bump the ci group with 3 updates by @dependabot in #1730
- build(deps): Bump serde_json from 1.0.134 to 1.0.135 in /functional-tests in the rust group by @dependabot in #1731
- buil

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.9.3/sops-v3.9.3.linux.amd64

# Move the binary in to your PATH
mv sops-v3.9.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.9.3/sops-v3.9.3.checksums.txt
curl -LO https://github.com/getsops/sops/releases/download/v3.9.3/sops-v3.9.3.checksums.pem
curl -LO https://github.com/getsops/sops/releases/download/v3.9.3/sops-v3.9.3.checksums.sig

# Verify the checksums file
cosign verify-blob sops-v3.9.3.checksums.txt \
--certificate sops-v3.9.3.checksums.pem \
--signature sops-v3.9.3.checksums.sig \
--certificate-identity-regexp= \
--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.9.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.9.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.9.3/sops-v3.9.3.intoto.jsonl

# Verify the provenance of the artifact
slsa-verifier verify-artifact <artifact> \
--provenance-path sops-v3.9.3.intoto.jsonl \
--source-uri github.com/getsops/sops \
--source-tag v3.9.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.9.3
- ghcr.io/getsops/sops:v3.9.3-alpine
Quay.io
- quay.io/getsops/sops:v3.9.3
- quay.io/getsops/sops:v3.9.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.9.3 \
--certificate-identity-regexp= \
--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 10 updates by @dependabot in #1699
- build(deps): Bump the ci group with 2 updates by @dependabot in #1698
- build(deps): Bump golang.org/x/crypto from 0.30.0 to 0.31.0 by @dependabot in #1703
- build(deps): Bump the ci group with 4 updates by @dependabot in #1708
- build(deps): Bump the rust group in /functional-tests with 2 updates by @dependabot in #1707
- CI: add 'persist-credentials: false' to checkout action

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.9.2/sops-v3.9.2.linux.amd64

# Move the binary in to your PATH
mv sops-v3.9.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.9.2/sops-v3.9.2.checksums.txt
curl -LO https://github.com/getsops/sops/releases/download/v3.9.2/sops-v3.9.2.checksums.pem
curl -LO https://github.com/getsops/sops/releases/download/v3.9.2/sops-v3.9.2.checksums.sig

# Verify the checksums file
cosign verify-blob sops-v3.9.2.checksums.txt \
--certificate sops-v3.9.2.checksums.pem \
--signature sops-v3.9.2.checksums.sig \
--certificate-identity-regexp= \
--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.9.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.9.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.9.2/sops-v3.9.2.intoto.jsonl

# Verify the provenance of the artifact
slsa-verifier verify-artifact <artifact> \
--provenance-path sops-v3.9.2.intoto.jsonl \
--source-uri github.com/getsops/sops \
--source-tag v3.9.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.9.2
- ghcr.io/getsops/sops:v3.9.2-alpine
Quay.io
- quay.io/getsops/sops:v3.9.2
- quay.io/getsops/sops:v3.9.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.9.2 \
--certificate-identity-regexp= \
--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 11 updates by @dependabot in #1645
- build(deps): Bump the ci group with 4 updates by @dependabot in #1644
- build(deps): Bump the go group with 12 updates by @dependabot in #1649
- build(deps): Bump the ci group with 5 updates by @dependabot in #1648
- build(deps): Bump the go group with 6 updates by @dependabot in #1653
- build(deps): Bump the ci group with 2 updates by @dependabot in #1654
- build(deps): Bump s

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.9.1/sops-v3.9.1.linux.amd64

# Move the binary in to your PATH
mv sops-v3.9.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.9.1/sops-v3.9.1.checksums.txt
curl -LO https://github.com/getsops/sops/releases/download/v3.9.1/sops-v3.9.1.checksums.pem
curl -LO https://github.com/getsops/sops/releases/download/v3.9.1/sops-v3.9.1.checksums.sig

# Verify the checksums file
cosign verify-blob sops-v3.9.1.checksums.txt \
--certificate sops-v3.9.1.checksums.pem \
--signature sops-v3.9.1.checksums.sig \
--certificate-identity-regexp= \
--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.9.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.9.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.9.1/sops-v3.9.1.intoto.jsonl

# Verify the provenance of the artifact
slsa-verifier verify-artifact <artifact> \
--provenance-path sops-v3.9.1.intoto.jsonl \
--source-uri github.com/getsops/sops \
--source-tag v3.9.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.9.1
- ghcr.io/getsops/sops:v3.9.1-alpine
Quay.io
- quay.io/getsops/sops:v3.9.1
- quay.io/getsops/sops:v3.9.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.9.1 \
--certificate-identity-regexp= \
--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
- Explicitly mark goreleaser's version, to avoid confusion with the Go version by @felixfontein in #1548
- build(deps): Bump the go group with 8 updates by @dependabot in #1550
- build(deps): Bump github/codeql-action from 3.25.10 to 3.25.11 in the ci group by @dependabot in #1551
- Fix the URL used for determining the latest SOPS version by @felixfontein in #1553
- build(deps): Bump the ci group with 4 updates by @dependabot in #1555
- build(deps): B

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.9.0/sops-v3.9.0.linux.amd64

# Move the binary in to your PATH
mv sops-v3.9.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.9.0/sops-v3.9.0.checksums.txt
curl -LO https://github.com/getsops/sops/releases/download/v3.9.0/sops-v3.9.0.checksums.pem
curl -LO https://github.com/getsops/sops/releases/download/v3.9.0/sops-v3.9.0.checksums.sig

# Verify the checksums file
cosign verify-blob sops-v3.9.0.checksums.txt \
--certificate sops-v3.9.0.checksums.pem \
--signature sops-v3.9.0.checksums.sig \
--certificate-identity-regexp= \
--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.9.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.9.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.9.0/sops-v3.9.0.intoto.jsonl

# Verify the provenance of the artifact
slsa-verifier verify-artifact <artifact> \
--provenance-path sops-v3.9.0.intoto.jsonl \
--source-uri github.com/getsops/sops \
--source-tag v3.9.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.9.0
- ghcr.io/getsops/sops:v3.9.0-alpine
Quay.io
- quay.io/getsops/sops:v3.9.0
- quay.io/getsops/sops:v3.9.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.9.0 \
--certificate-identity-regexp= \
--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
- Respect aws_profile from Keygroup Config by @Kouzukii in #1049
- build(deps): Bump the go group with 6 updates by @dependabot in #1327
- build(deps): Bump the go group with 3 updates by @dependabot in #1328
- build(deps): Bump the go group with 1 update by @dependabot in #1330
- build(deps): Bump github.com/docker/docker from 20.10.24+incompatible to 24.0.7+incompatible by @dependabot in #1336
- build(deps): Bump the go group with 3 updates by @depe

GitHub Container Registry
- ghcr.io/getsops/sops:v3.8.1
- ghcr.io/getsops/sops:v3.8.1-alpine
Quay.io
- quay.io/getsops/sops:v3.8.1
- quay.io/getsops/sops:v3.8.1-alpine
What's Changed
- build(deps): Bump the ci group with 3 updates by @dependabot in #1295
- pgp: improve handling of GnuPG home dir by @hiddeco in #1298
- Delete sops encrypted file we don't have keys for by @felixfontein in #1288
- Improve handling of errors when binary store handles bad data by @felixfontein in #1289
- On macOS, prefer XDG_CONFIG_HOME over os.
UserConfigDir() by @felixfontein in #1291
- Do not crash if an empty YAML file is encrypted by @felixfontein in #1290
- Fix descriptions of unencrypted-regex and encrypted-regex flags, and ensure unencrypted_regex is considered in config validation by @mitar in #1300
- build(deps): Bump the go group with 4 updates by @dependabot in #1306
- build(deps): Bump the ci group with 1 update by @dependabot in #1301
- Handle return values of dec.
Token() to improve error messages by @felixfontein in #1307
- pgp: make error the last return value by @felixfontein in #1310
- pgp: do not require abs path for SopsGpgExecEnv by @holiman in #1309
- decrypt: fix dropped error by @alrs in #1304
- Handle errors by @felixfontein in #1311
- Report key rotation errors by @felixfontein in #1317
- cmd/sops/main.go: make sure to wrap raw errors with toExitError() by @felixfontein in #1318
- build(deps): Bump the go group with 7 updates by @dependabot in #1319
- Enrich AWS authentication documentation by @nsantiago2719 in #1272
- Better error reporting for missing gpg binary by @makkes in #1286
- Improve RST and MD files by @felixfontein in #1320
- Add linting for RST and MD files by @felixfontein in #1287
- Update dependencies by @hiddeco in #1325
- Prepare v3.8.1 by @hiddeco in #1324
New Contributors
- @mitar made their first contribution in #1300
- @holiman made their first contribution in #1309
- @alrs made their first contribution in #1304
- @nsantiago2719 made their first contribution in #1272
- @makkes made their first contribution in #1286

GitHub Container Registry
- ghcr.io/getsops/sops:v3.8.0
- ghcr.io/getsops/sops:v3.8.0-alpine
Quay.io
- quay.io/getsops/sops:v3.8.0
- quay.io/getsops/sops:v3.8.0-alpine
What's Changed
- chore: update dependencies by @hiddeco in #1275
- build: pin actions to full length commit SHA and add CodeQL by @hiddeco in #1276
- Enable Dependabot for Docker, GitHub Actions and Go Mod by @hiddeco in #1277
- build(deps): Bump the go group with 2 updates by @dependabot in #1280
- build(deps): Bump the ci group with 6 updates by @dependabot in #1279
- release: generate versioned .intoto.jsonl by @hiddeco in #1278
- pgp: remove DisableAgent option by @hiddeco in #1282
- keyservices: address logging regression by @hiddeco in #1281
- chore: update dependencies by @hiddeco in #1283
- Prepare v3.8.0 by @hiddeco in #1284

## Changes:

- Upgrade dependencies (#1024, #1045)
- Build alpine container in CI (#1018, #1032, #1025)
- keyservice: accept KeyServiceServer in LocalClient (#1035)
- Add support for GCP Service Account within GOOGLE_CREDENTIALS (#953)

## Bug fixes:

- Upload the correct binary for the linux amd64 build (#1026)
- Fix bug when specifying multiple age recipients (#966)
- Allow for empty yaml maps (#908)

## Commits

- [75cd389]: Add a test to reproduce #907 (ikedam) #908
- [108b211]: Allow empty maps for yaml (#907) (ikedam) #908
- [ea8b3bb]: support gcp credentials as env var (Kaplinsky, Joshua B) #953
- [c0dc484]: Update keysource.go (Josh Kaplinsky) #953
- [63fa89c]: Merge remote-tracking branch 'remotes/origin/develop' into feature/907_FixEmptyYaml
(ikedam) #908
- [b926cf9]: Build alpine container in CI (#870) (ikedam) #1018
- [234bf9f]: Upgrade all dependencies (AJ Bahnken) #1024
- [4277de4]: Remove duplicated stage from Dockerfile.alpine (Shouichi Kamiya) #1025
- [605fb27]: Explicitly build linux amd64 binary (Janis Peisenieks) #1026
- [7ebee3d]: This fixes a bug with age encryption when specifying multiple age recipients (Cedric
Kienzler) #966
- [b5f5f28]: Make masterKeyFromRecipient private (Cedric Kienzler) #966
- [1dc90ad]: Add tests for single key (Cedric Kienzler) #966
- [3875b00]: Use latest dockerd in CI to allow build alpine image (#870) (ikedam) #1032
- accept KeyServiceServer in LocalClient #1035 (Hidde Beydals)
- [1bb30e2]: Limit role session name length to 64 characters. (AJ Bahnken) #1037
- [a01208c]: Update golang.org/x/crypto (Hidde Beydals) #1045
- [e128fa2]: Update keyservice implementation dependencies (Hidde Beydals) #1045
- [220b652]: Update golang.org/x/{net,oauth2,sys} dependencies (Hidde Beydals) #1045
- [477b61f]: Update remaining dependencies (Hidde Beydals) #1045
- [25817ed]: Replace x/crypto/openpgp with ProtonMail/go-crypto (Hidde Beydals) #1045
- [07aea97]: Merge remote-tracking branch 'upstream/develop' into develop (Josh Kaplinsky) #953
- [4ffb54c]: Use custom GOOGLE_CREDENTIALS or fallback to default (Josh Kaplinsky) #953
- [17fb03f]: Merge remote-tracking branch 'upstream/develop' into develop (Josh Kaplinsky) #953
- [15583bd]: prep for v3.7.3 (AJ Bahnken) #1053