You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 9ca5420
Browse filesBrowse the repository at this point in the historyBrowse files
- Release archives cover aarch64-unknown-linux-gnu and x86_64-apple-darwin
next to the existing three; ARCHIVE_TARGETS, ARCHIVE_PLATFORMS, host
classes, packager admission, CI matrix and publication lists move
together, and v0.8.0-era three-platform manifests still verify (#560).
- Linux archives are built in an ubuntu:22.04 container; the packager
rejects any GLIBC requirement above 2.35, pins and checks the macOS
deployment target, and records a per-archive runtime object (#555).
- The aggregate manifest gains an optional installers inventory
(install.sh, install.ps1) checked against SHA256SUMS, parsed by
release_provenance and re-hashed by doctor verify-release.
- Release notes lead with an Install section derived from the actual
assets and collapse the changelog; archive README.md is rendered from
per-platform templates with tag-pinned links and the first-project
journey (#554).
Co-Authored-By: Claude Opus 5.5 <[email protected]>
`github-hosted-macos-15`, `github-hosted-macos-15-intel` and
53
+
`github-hosted-windows-2025`; the aggregate provenance is generated on the
54
+
Ubuntu 24.04 publisher. The v0.8.0 manifest and provenance, which carry the
55
+
original three platforms, remain verifiable; a manifest or provenance for a
56
+
later version must inventory all five.
57
+
58
+
### Runtime baseline
59
+
60
+
Each archive records the lowest runtime it supports, and the packager rejects
61
+
a build that exceeds it.
62
+
63
+
| Target | Baseline | How it is enforced |
64
+
| --- | --- | --- |
65
+
| Linux (x86_64, aarch64) | GNU/Linux, glibc 2.35 | Built by `scripts/package-release-linux-container.sh` inside `ubuntu:22.04` with the pinned 1.97.1 toolchain; `package-release.sh` reads every `GLIBC_x.y` requirement with `readelf --version-info` (or `objdump -T`) and fails above 2.35. The smoke runs on the container's glibc 2.35. musl is not supported. |
66
+
| macOS Apple Silicon | macOS 11.0 |`MACOSX_DEPLOYMENT_TARGET=11.0`; the binaries' `LC_BUILD_VERSION` minos is read with `vtool -show-build` (or `otool -l`) and must not exceed 11.0. |
67
+
| macOS Intel | macOS 10.12 |`MACOSX_DEPLOYMENT_TARGET=10.12`, checked the same way. |
68
+
| Windows x64 | Windows 10 1809 (10.0.17763) / Server 2019 | Recorded; imported DLLs are listed from `dumpbin /dependents` only when `dumpbin` is available, otherwise recorded as `null` (not inspected). |
69
+
70
+
The per-archive `release-manifest.json` (`semaprax.release-artifact.v1`) gains
71
+
a `runtime` object: `os`, `min_os_version` (null on Linux), `cpu`,
72
+
`libc_family` (`glibc`, `libsystem` or `ucrt`), `min_libc_version` (the
73
+
highest glibc requirement actually found on Linux, otherwise null) and
74
+
`dynamic_libraries` (sorted `NEEDED`/`otool -L`/`dumpbin` names, or null when
75
+
not inspected). It is recorded evidence of the built binaries, not an
76
+
authority; the runtime-baseline row of the matrix is unchanged.
77
+
48
78
Each archive contains `semaprax`, `semapraxd`, `LICENSE`, `README.md`, a fixed
49
79
smoke program, and the deterministic `semaprax.release-artifact.v1` manifest.
80
+
The archive `README.md` is rendered from `packaging/archive/README.unix.md` or
81
+
`README.windows.md` by replacing exactly `{{TAG}}`, `{{VERSION}}` and
82
+
`{{TARGET}}`: it states the contents, runtime requirements, local invocation and
83
+
`PATH` steps and the first-project journey, and every link is an absolute
84
+
URL pinned to the release tag. The repository README is not packaged.
50
85
The archive's `semaprax` is the unpublished `semaprax-toolchain` package's
51
86
`semaprax-full` binary, renamed during staging. The standalone crates.io
52
87
package excludes private Native Rust package publication, Windows revision-store
@@ -405,14 +440,23 @@ SLSA provenance for its own already smoke-tested archive. The final
405
440
`publish-release` job alone receives `contents: write` and, after both
406
441
`release-gate` and every artifact-matrix child succeed, the separate OIDC
407
442
capability needed to sign the final aggregate provenance. It authenticates the
408
-
exact three-archive inventory, writes one `SHA256SUMS`, creates the final
443
+
exact five-archive inventory, writes one `SHA256SUMS`, creates the final
409
444
manifest and provenance, and keylessly signs that provenance before publishing
410
445
a regular GitHub release. No repository signing key exists. The publisher
411
-
derives the body with `scripts/release-notes.py`: it
412
-
selects only the tagged version's dated `CHANGELOG.md` section, stopping at the
413
-
next release heading, and surrounds it with the release nonclaims. A missing,
414
-
duplicate, or empty section fails the publication instead of silently creating
415
-
incomplete notes.
446
+
derives the body with `scripts/release-notes.py --assets-dir dist`: the body
447
+
opens with an Install section (version, a host/CPU to exact-tag archive table
448
+
derived from the asset directory and checked against the admitted targets,
449
+
installer one-liners only when `install.sh`/`install.ps1` are among the assets,
450
+
a link to the exact-tag install guide, one line separating runnable archives
451
+
from GitHub's source snapshots and verification metadata, and a verification
452
+
pointer). It then selects only the tagged version's dated `CHANGELOG.md`
453
+
section, stopping at the next release heading, inside a collapsed
454
+
`<details>` block, and closes with the release nonclaims. The changelog bound
455
+
subtracts the size of that frame from the GitHub body limit. A missing admitted
456
+
archive, or a missing, duplicate, or empty changelog section, fails the
457
+
publication instead of silently creating incomplete notes. Without
458
+
`--assets-dir` only the asset-independent guidance is rendered (no table, no
459
+
one-liners).
416
460
417
461
## Canonical release manifest
418
462
@@ -429,7 +473,18 @@ distinct from the narrower per-archive `semaprax.release-artifact.v1` manifest
429
473
`scripts/package-release.sh`/`.ps1` embed inside each single archive: that
430
474
document is written before any sibling archive or its digest exists, so it can
431
475
only assert what one packaging run knows about itself. This one is built once,
432
-
after every target archive exists, from the sibling archives' actual bytes:
476
+
after every target archive exists, from the sibling archives' actual bytes.
477
+
478
+
The manifest also carries one optional key, `installers`: an array of
479
+
`{name, size, digest}` for the bootstrap scripts `install.sh` and `install.ps1`
480
+
when they sit in `--archives-dir` (they are published byte-identical to the
481
+
tagged `scripts/install.sh` and `scripts/install.ps1`). Entries are sorted by
482
+
name, the name set is closed to those two, and, when a sibling `SHA256SUMS` is
483
+
present, each installer must be listed there with the same digest. The key is
484
+
omitted when neither script is present, which is the shape of every release
485
+
through v0.8.0; consumers must accept both shapes.
486
+
`semaprax::release_provenance::parse_manifest` does, and
487
+
`verify_manifest_artifacts_on_disk` re-hashes installers as well as archives.
Copy file name to clipboardExpand all lines: docs/RELEASE-SIGNING-POLICY-V1.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -138,7 +138,7 @@ manifest even if the edit reparses to the same JSON value.
138
138
|`builder.run_id` / `builder.run_attempt`| strings | The workflow run that produced this document, for operator traceability. Not independently verified -- see nonclaims. |
139
139
|`toolchain.rustc_version`| string | The Rust compiler version used to build the release binaries. |
140
140
|`toolchain.cargo_locked`| boolean | Always `true`: every packaging command in `docs/RELEASE-PROCESS.md` uses `--locked`. |
141
-
|`build_host_class`| string | The admitted hosted runner that generated this aggregate provenance document, not a claim that every listed archive was built on that host. Each archive's separate GitHub attestation carries its own matrix builder identity. One of `github-hosted-ubuntu-24.04`, `github-hosted-macos-15`, `github-hosted-windows-2025` from `docs/RELEASE-PROCESS.md`. |
141
+
|`build_host_class`| string | The admitted hosted runner that generated this aggregate provenance document, not a claim that every listed archive was built on that host. Each archive's separate GitHub attestation carries its own matrix builder identity. One of `github-hosted-ubuntu-24.04`, `github-hosted-ubuntu-24.04-arm`, `github-hosted-macos-15`, `github-hosted-macos-15-intel`, `github-hosted-windows-2025` from `docs/RELEASE-PROCESS.md`. |
142
142
|`nonclaims`| array of strings | What this document does not assert (see below); never empty. |
143
143
144
144
This document is generated **before** publication (like the manifest it
@@ -374,8 +374,9 @@ document says about itself is trusted.
374
374
The standalone binary uses the pure `SigstoreOfflineVerifier` when the
375
375
directory presents the complete v0.3 offline inventory:
376
376
`release-provenance.bundle`, `trusted_root.jsonl`, and one
377
-
`release-attestation-<admitted-target>.json` for each of this policy's three
378
-
closed archive targets. An embedding host may explicitly replace that default
377
+
`release-attestation-<admitted-target>.json` for each of this policy's
378
+
closed archive targets (three through v0.8.0, five afterwards: the two Linux
379
+
and two macOS targets plus Windows). An embedding host may explicitly replace that default
379
380
with another `OfflineBundleVerificationCapability`; the CLI adapter still reads
380
381
the complete bounded inventory and passes its exact bytes to
381
382
`verify_offline_release_with_capability`. A partial inventory fails as a
@@ -542,7 +543,7 @@ historical evidence are changed.
542
543
```
543
544
followed by uploading `release-manifest.json`, `release-provenance.json`,
544
545
`release-provenance.bundle`, `release-signature-claim.json`, and
545
-
`trusted_root.jsonl` as release assets alongside the three archives and
546
+
`trusted_root.jsonl` as release assets alongside the archives (and `install.sh`/`install.ps1` when present) and
546
547
their attestations. The source-locked CI contract requires this order and
547
548
exact asset set. The trusted root is fetched while the publisher is online;
548
549
later offline verification receives those exact bytes explicitly and never
This is the SEMAPRAX {{VERSION}} command-line toolchain for `{{TARGET}}`.
4
+
SEMAPRAX is beta software: see the [release page](https://github.com/wavect/semaprax/releases/tag/{{TAG}}) for what is and is not claimed.
5
+
6
+
## What is in this folder
7
+
8
+
| File | What it is |
9
+
| --- | --- |
10
+
|`semaprax`| The full `semaprax` command-line tool |
11
+
|`semapraxd`| The SEMAPRAX daemon used by editors and agents |
|`release-manifest.json`| Version, commit, target and runtime requirements of this build |
14
+
|`smoke/meaning.spx`| A one-function sample used to smoke-test this archive |
15
+
|`README.md`| This file |
16
+
17
+
## Runtime requirements
18
+
19
+
- Linux: a GNU/Linux system with glibc 2.35 or newer (Ubuntu 22.04 or newer, Debian 12 or newer). musl-based systems such as Alpine are not supported.
20
+
- macOS: macOS 11 or newer on Apple Silicon, macOS 10.12 or newer on Intel.
21
+
- Exact requirements of this archive are recorded under `runtime` in `release-manifest.json`.
22
+
23
+
## Run it from this folder
24
+
25
+
Open a terminal in this folder and run:
26
+
27
+
```sh
28
+
./semaprax --version
29
+
```
30
+
31
+
If macOS refuses to open the program after a browser download, remove the download quarantine mark once:
32
+
33
+
```sh
34
+
xattr -dr com.apple.quarantine .
35
+
```
36
+
37
+
## Put it on your PATH
38
+
39
+
For the current terminal only:
40
+
41
+
```sh
42
+
export PATH="$PWD:$PATH"
43
+
semaprax --version
44
+
```
45
+
46
+
To keep it, move this folder somewhere permanent and add its path to your shell profile. The installer script does this for you; see the [install guide](https://github.com/wavect/semaprax/blob/{{TAG}}/handbook/getting-started/install.md).
47
+
48
+
## Your first project
49
+
50
+
From any empty working directory, with `semaprax` on your PATH:
51
+
52
+
```sh
53
+
semaprax --version
54
+
semaprax new first-semaprax
55
+
semaprax check first-semaprax/semaprax.toml
56
+
semaprax test first-semaprax/semaprax.toml
57
+
semaprax run first-semaprax/semaprax.toml
58
+
```
59
+
60
+
The last command prints `42`.
61
+
62
+
To try the bundled sample without creating a project:
-[Your first project](https://github.com/wavect/semaprax/blob/{{TAG}}/handbook/getting-started/first-project.md)
-[Quick reference for writing `.spx` source](https://github.com/wavect/semaprax/blob/{{TAG}}/docs/AGENT-QUICK-REFERENCE.md)
75
+
-[Verifying a release](https://github.com/wavect/semaprax/blob/{{TAG}}/docs/RELEASE-PROCESS.md)
This is the SEMAPRAX {{VERSION}} command-line toolchain for `{{TARGET}}`.
4
+
SEMAPRAX is beta software: see the [release page](https://github.com/wavect/semaprax/releases/tag/{{TAG}}) for what is and is not claimed.
5
+
6
+
## What is in this folder
7
+
8
+
| File | What it is |
9
+
| --- | --- |
10
+
|`semaprax.exe`| The full `semaprax` command-line tool |
11
+
|`semapraxd.exe`| The SEMAPRAX daemon used by editors and agents |
|`release-manifest.json`| Version, commit, target and runtime requirements of this build |
14
+
|`smoke\meaning.spx`| A one-function sample used to smoke-test this archive |
15
+
|`README.md`| This file |
16
+
17
+
## Runtime requirements
18
+
19
+
- Windows 10 version 1809 (build 17763) or newer, or Windows Server 2019 or newer, on x64.
20
+
- Exact requirements of this archive are recorded under `runtime` in `release-manifest.json`.
21
+
22
+
## Run it from this folder
23
+
24
+
Open PowerShell in this folder and run:
25
+
26
+
```powershell
27
+
.\semaprax.exe --version
28
+
```
29
+
30
+
If Windows SmartScreen warns about a downloaded copy, these programs are not code-signed in this release; verify the download first as described in the [release process](https://github.com/wavect/semaprax/blob/{{TAG}}/docs/RELEASE-PROCESS.md).
31
+
32
+
## Put it on your PATH
33
+
34
+
For the current PowerShell window only:
35
+
36
+
```powershell
37
+
$env:Path = "$PWD;$env:Path"
38
+
semaprax --version
39
+
```
40
+
41
+
To keep it, move this folder somewhere permanent and add its path to your user `Path` in Windows Settings. The installer script does this for you; see the [install guide](https://github.com/wavect/semaprax/blob/{{TAG}}/handbook/getting-started/install.md).
42
+
43
+
## Your first project
44
+
45
+
From any empty working directory, with `semaprax` on your `Path`:
46
+
47
+
```powershell
48
+
semaprax --version
49
+
semaprax new first-semaprax
50
+
semaprax check first-semaprax\semaprax.toml
51
+
semaprax test first-semaprax\semaprax.toml
52
+
semaprax run first-semaprax\semaprax.toml
53
+
```
54
+
55
+
The last command prints `42`.
56
+
57
+
To try the bundled sample without creating a project, run these from this folder:
-[Your first project](https://github.com/wavect/semaprax/blob/{{TAG}}/handbook/getting-started/first-project.md)
-[Quick reference for writing `.spx` source](https://github.com/wavect/semaprax/blob/{{TAG}}/docs/AGENT-QUICK-REFERENCE.md)
70
+
-[Verifying a release](https://github.com/wavect/semaprax/blob/{{TAG}}/docs/RELEASE-PROCESS.md)
0 commit comments