PermeantOS Back to site

Validated early platform

Release Artifacts

Build, validate, verify, and install pre-publication PermeantOS binary bundles.

PermeantOS now has pre-publication release artifact tooling. It builds checksummed binary archives, emits a machine-readable manifest, and validates candidate or tag artifact sets before anything is published. It still does not create GitHub Releases or publish crates.

Build Locally

scripts/build-release-artifacts.py   --version v0.1.30-platform   --out-dir dist/release

The output includes:

  • permeantos-<version>-<target>.tar.gz
  • checksums.txt
  • release-manifest.json

Validate

scripts/check-package-readiness.py --json-out dist/release/package-readiness.json
scripts/validate-release.py \
  --version v0.1.30-platform \
  --artifact-dir dist/release \
  --package-readiness dist/release/package-readiness.json \
  --json-out dist/release/release-validation.json

release-validation.json records the tag format, changelog promotion check, artifact manifest validation, archive checksums, required archive members, and package-readiness status. Tag-triggered workflow runs are strict; manual candidate runs can allow the current Unreleased changelog section before final promotion.

Verify

shasum -a 256 -c checksums.txt
tar -tzf permeantos-<version>-<target>.tar.gz

Install

tar -xzf permeantos-<version>-<target>.tar.gz
export PATH="$PWD/permeantos-<version>-<target>/bin:$PATH"
permeant-cli --help

Run the starter migration demo from the installed binary:

permeant-cli starter-demo --seq-len 128 --out-dir .permeant-demo

The demo writes .permeant-demo/starter-demo-report.json with schema permeantos-starter-demo-v0.

Publishing Boundary

GitHub Release creation, signed assets, crates.io publishing, and Python package publishing are still intentionally gated. The current workflows build and validate artifacts, then upload workflow artifacts only. Real publishing requires the publishing policy gate, credentials through the intended secure path, release validation, signing policy, rollback ownership, and an explicit request for that release mode.

The repository now also includes a package-readiness gate for Rust crates and the Python SDK. That gate verifies package metadata and keeps every registry package explicitly publish-disabled until the real-release policy is complete.