frontier-sdk Updates & Release Notes

Frontier Foundation 0.1.0-rc.1 is the first reproducible release-candidate assembly for the public governed-worker foundation.

Included package versions

@frontier-infra/[email protected]

@frontier-infra/[email protected]

@frontier-infra/[email protected]

@frontier-infra/[email protected]

@frontier-infra/[email protected]

@frontier-infra/[email protected]

The four new packages were published with the npm next dist-tag. Because these were first publications, npm also assigned latest to the same 0.1.0 version automatically; no separate later-version promotion occurred.

Proven by the hosted release gate

deterministic release reconstruction from the annotated tag;

Node, Python, TypeScript consumer, chaos-corpus, snapshot, starter, and package gates;

byte-for-byte npm registry integrity matching the verified release tarballs;

npm-generated SLSA provenance attestations for the four newly published packages;

clean external create-frontier-app@next scaffold, install, and production build.

Release source: ff160b1631d4ca2091a9f326c2da9ac35d5651d4

Hosted release evidence: https://github.com/frontier-infra/frontier-sdk/actions/runs/31612155975

Post-tag custody hardening on main: 0fbbe6da3f5297a8bf4270f17e84d506966732b9

Known non-claim: Docker image build and runtime execution remain unverified because the local Docker/Colima daemon was unavailable. Compose configuration validation is not equivalent to an image/runtime proof.

Next milestone recommendation: Conductor's first governed live-effect deployment, kept separate from this frozen RC.