3 Commits

Include renames

Author	SHA1	Message	Date
jcoffey-dev	3d3b302129	release: check out the changelog before downloading the archives ... The release job checked out CHANGELOG.md after downloading the archives into dist/, and a checkout cleans the workspace, so the archives were gone by the time they were uploaded ("uploading *", curl exit 26). The first v2026.9.30 run failed there and removed its draft; nothing was published. The checkout now runs first. The job also checks that both archives and SHA256SUMS are present before it creates a release, and says which is missing if one is.	2026-09-30 15:19:22 -07:00
jcoffey-dev	7156c925e7	Prepare the 2026.9.30 release, with notes from the changelog ... The changelog's first section becomes 2026.9.30 and gains the phase 1 and 2 changes: re-export updates, one copy per message, the Sieve rename, timeouts, scoped certificate checks, resilient and bounded imports, batched export with progress, and the predictive dry run. The tag build now takes each release's notes from its version's section of CHANGELOG.md, followed by the line about the binaries, so the release and the announcement made from it say what changed. A version with no section falls back to that line alone.	2026-09-30 14:13:17 -07:00
jcoffey-dev	42413563ef	Replace the release tooling with the suite's CI ... Upstream's cargo-dist pipeline published to npm and Homebrew under its own names, built an MSI, and ran on every pull request. It goes, with its dist-workspace.toml, the wix/ installer files and the README image. CI now follows the rest of the suite. .gitea/workflows runs `cargo test --locked` on Gitea's runners, or, when the org variable BUILD_ON is 'github', waits for the result GitHub reports on the commit. On GitHub, .github/workflows/ci.yml runs the same tests, and for a v* tag on main whose version matches Cargo.toml builds scripts/build-release.sh on native amd64 and arm64 runners (Ubuntu 22.04, for the widest glibc range), attaches inbuxa-migrate-linux-{amd64,arm64}.tar.gz and SHA256SUMS to the Gitea Release, copies the Release to GitHub, and reports back. Releases are built only on GitHub; with BUILD_ON unset a tag is tested but not released. Published releases are announced on the forum.	2026-09-30 10:12:48 -07:00