Docs · Releases
Releases
A release is what landed since the last one, built for every platform, signed and published, with notes written from the changes' proof.
Cutting one
anvil release new 1.4.0 --project harbor
Anvil drafts the notes from the changes merged since the last release: one line each, in plain words, from what each change's proof says is now true. Edit them, then publish.
Builds
# .aide/config.toml [release] build = "scripts/build.sh" on = ["macos-arm64", "linux-amd64", "linux-arm64", "windows-amd64"] sign = "release-key"
Each target builds on a machine of that platform and architecture. A build that fails goes to a thread like a failing check, and the release waits.
Publishing
Published builds are signed with the project's Ed25519 key and listed with their SHA-256 sums. Installed copies that check for updates are offered the new version with its notes, and verify the signature before they install it.
With publish a release in the project's asks, a thread that's prepared a release asks you before it publishes.
After it ships
The issues the release closes are told which version fixed them, and so are the people following them. What users report from inside the new version arrives as issues, with the version, the platform and what they were doing.