aboutsummaryrefslogtreecommitdiffstats
path: root/scripts/release
Commit message (Collapse)AuthorAgeFilesLines
* scripts/wire-check: a swarm of the last release and this treetv2 days1-2/+5
| | | | | | | | | | | | | | | | Four nodes on this host over libp2p on loopback, two of a release tag's build and two of this tree's, in turns, each seeded with the one before. Where the two builds' wire versions meet, each node writes, and the check is that every node reads what each wrote and that none logs a peer of another wire version. Where they don't, that the tag's nodes log this tree's as such, so their operators know to upgrade. scripts/release runs it against the last release, after saying from the two builds' --version how the release upgrades: so a release that says it rolls out node by node has been seen to. docs/development.md says how a change to the wire format is made: a new version beside the ones spoken already, the older kept frozen.
* scripts/release: a release checked, said how it upgrades, committed and taggedtv2 days1-0/+184
Releases were made by hand: a commit, a tag, and whatever one remembered to check. `scripts/release [--dry-run] X.Y.Z` makes one: 1. the tree clean, notes under Unreleased in CHANGELOG.md, the version later than the last v* tag's; 2. the version set in Cargo.toml and Cargo.lock (and the --version example in operations.md), then `cargo quick`, `cargo sim` and scripts/federation-check, stopping at the first that fails and leaving the tree as it was; 3. this build's `continuum --version` against the last release's, built in a cache of its own: node by node where their wire versions meet and Automerge is the same, every node together where they don't share one, which from 1.0.0 on it refuses but in a major release; Automerge changed, no remake until every node runs it; 4. the Unreleased notes become the release's, headed by what it found; the commit `release X.Y.Z`, tagged vX.Y.Z with that, what the build speaks and knows, and the notes; and federation-<F>.<R> too where the build knows a later revision than the last release. It pushes nothing. With --dry-run it checks and prints what it would write. docs/development.md says how releases are made.