Skip to content

docs: align current release coordinates #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
chen21019 merged 1 commit into from
Sep 9, 2026
Merged

docs: align current release coordinates #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ PastureStack is an independent community effort to preserve, audit, and moderniz

## Project status

The `v0.3.0` maintenance layer is based on the preserved upstream `v0.2.2` boundary. It uses Go modules and the exact Go 1.27.0 toolchain, deterministic Release packaging, bounded JSON requests, HTTP resource timeouts, scoped Vault storage operations, neutral product naming, race tests, a 70% critical-path coverage gate, and a loopback local-key API integration test. Production deployment remains disabled until the matching Server integration has passed in an isolated VM.
The current `v0.3.1` maintenance release is based on the preserved upstream `v0.2.2` boundary and is consumed by PastureStack Server `v1.6.410`. It uses Go modules and the exact Go 1.27.0 toolchain, deterministic Release packaging, bounded JSON requests, HTTP resource timeouts, scoped Vault storage operations, neutral product naming, race tests, a 70% critical-path coverage gate, and a loopback local-key API integration test.

The `none` backend is an insecure compatibility fixture and is disabled by default. It can be enabled only with `--allow-insecure-none-backend` or `ALLOW_INSECURE_NONE_BACKEND=true` for an explicitly reviewed legacy migration. The supported Server path uses the `localkey` backend on the loopback interface.

Expand All @@ -24,7 +24,7 @@ make package
make ci
```

For the reviewed compatibility release, set `VERSION_OVERRIDE=v0.3.0` and `SOURCE_DATE_EPOCH=0`. Packaging produces `secret-delivery-api-0.3.0-linux-amd64.tar.xz`. PastureStack Server downloads the flat asset from its matching GitHub Release, verifies its SHA-256 digest, and installs the executable under the preserved `secrets-api` compatibility name. Operators do not need to host an artifact mirror.
For the reviewed compatibility release, set `VERSION_OVERRIDE=v0.3.1` and `SOURCE_DATE_EPOCH=0`. Packaging produces `secret-delivery-api-0.3.1-linux-amd64.tar.xz`. PastureStack Server downloads the flat asset from its matching GitHub Release, verifies its SHA-256 digest, and installs the executable under the preserved `secrets-api` compatibility name. Operators do not need to host an artifact mirror.

See [COMPATIBILITY.md](COMPATIBILITY.md), [SECURITY.md](SECURITY.md), [ORIGIN.md](ORIGIN.md), and [THIRD-PARTY-NOTICES.md](THIRD-PARTY-NOTICES.md).

Expand Down