Skip to content

v0.0.7

Choose a tag to compare

@github-actions github-actions released this 11 Nov 04:45
· 101 commits to main since this release
ec74349

Release 0.0.7

Pregate v0.0.7, core 0.0.1. macOS ARM64 stays the stable platform. Linux and Windows archives stay experimental until native validation is recorded.

Install 0.0.7, then review the project update it prepares (pregate update --project --preview) and approve that exact digest. A global update prepares that review for each enabled project whose lock still pins an older engine.

This is a small release. It adds one command and one guide. No rule, no pack and no contract format changed, and the hooks decide as they did in 0.0.6.

A launcher the project owns

pregate project launcher --preview prepares a launcher inside the project, at .pregate/bin/pregate (on Windows, pregate.cmd and project-launcher.ps1). It goes through the same review and approval as a contract change.

  • The launcher runs the engine that the project's lock pins, from the user cache. It never falls back to a launcher on PATH.
  • A hook call with a missing or empty cached engine denies, and names the reason.
  • The command needs a valid engine pin and that engine in the cache; pregate prepare puts it there.
  • pregate install keeps this launcher. It removes only the launcher that 0.1.0 committed at the same path.

This is the first step toward a project that does not depend on a machine-wide setup. The harness registrations still come from pregate setup; nothing in this release moves them into the project.

Maintenance, rebuild and rollback

Maintenance, reproducible build and rollback says who releases Pregate, how to build a tag from a clean checkout, how a published archive is verified, and how a pinned project is upgraded and rolled back.

An end-to-end test runs the upgrade and the rollback on every CI run, with two real engines that differ only in version: the upgrade changes the pin and no rule, both engines deny the same edit for the same rule, and reverting the upgrade commit restores the first committed contract.

The page states what a rebuild does not prove. Two local builds of one commit were identical. A local build of v0.0.5 did not match the published archive.

How the project tests itself

  • CI takes about half the time. The Linux job ran the whole suite twice, once inside a fresh clone that the job already is. The Windows job ran four suites twice in one serial job that took 29 to 45 minutes against a 45-minute limit. Each suite now runs once, and Windows runs in three parallel jobs. On the runs measured, the Linux job went from 39 to 19 minutes and the slowest Windows job from 29–45 to 14 minutes.
  • The suites start fewer and cheaper processes. 3% of the tests used 83% of the Windows time, and the cost was process starts. Suites that ran the engine from source run the compiled engine, and about 40 files share one engine build per test process. No assertion changed.
  • Hook latency is also read against the last release. The hosted macOS runner's own speed varied 3.4 times over 60 runs, and the regression gate compares with a fixed number: it failed on unchanged code, and on a fast runner a hook three times slower would have passed. The latency jobs now also time the last release's engine and the current one in turn on the same runner and report the ratio. That reading informs; it fails nothing yet.
  • Deadline tests bound the mechanism, not the machine. Three tests put their bound on the life of the process the deadline ends, not on the whole command. No timeout was raised.

What this release does not establish

  • The project launcher is one piece. No harness was run end to end from a project with no machine-wide setup.
  • The ratio against the last release has no limit yet. Its spread on hosted runners is being collected; the fixed latency gate is unchanged and still fails by runner noise at times.
  • The deadline tests were not validated on a low-memory Windows machine.
  • The full suite does not run on macOS in CI. macOS runs the latency and release-build jobs there, and the suite on the maintainer's machine.

The changelog lists every change. Guarantees and limits did not change.