diff options
| author | tv <tv@krebsco.de> | 2026-11-19 17:27:17 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-19 19:25:55 +0100 |
| commit | 180aba9ff89a4a294e284aa281d96adbcfe1b85b (patch) | |
| tree | 5cf9e1cc989e3f7fbab14347f40ec0ff06b3a655 /src/swarm/refusals.rs | |
| parent | eeec08b8d15ac3c3301060c71772a664bd2a4685 (diff) | |
scripts/release: a release checked, said how it upgrades, committed and tagged
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.
Diffstat (limited to 'src/swarm/refusals.rs')
0 files changed, 0 insertions, 0 deletions
