Skip to content

Release 4.2.0: prebuilt binaries workflow, changelog, install docs - #2

Merged
Mattbusel merged 2 commits into
mainfrom
release/4.2.0
Sep 25, 2026
Merged

Mattbusel merged 2 commits into
mainfrom
release/4.2.0

Conversation

@Mattbusel

Copy link
Copy Markdown
Owner

Prepares 4.2.0, the first release since 4.1.2 (crates.io is at 4.1.2; Cargo.toml already said 4.2.0 but it was never tagged or published).

  • .github/workflows/release.yml: on a vX.Y.Z tag, builds every-other-token for Linux x86_64 (gnu, built on Ubuntu 22.04 for glibc compatibility), macOS arm64 and x86_64, and Windows x86_64, packages each with README and LICENSE, and attaches the archives plus SHA-256 checksums to a GitHub Release. Can also be re-run for an existing tag via workflow_dispatch. It does not publish to crates.io. On PRs that touch this file it runs the build matrix only (no release), which is how this PR tests it.
  • CHANGELOG: a 4.2.0 section with the fixes from Get CI green: fix stale tests, mock provider bugs, add no-key example #1 and a pointer to the modules added since 4.1.2. The old "Unreleased" notes are kept under it; their line claiming a release workflow that also published to crates.io is removed because that workflow was deleted in March.
  • README install: points to prebuilt binaries on the latest release, then cargo install.
  • CONTRIBUTING: commands that actually match CI (cargo test), the no-key demo, and an honest note that clippy -D warnings is not enforced yet (86 existing warnings).

cargo publish --dry-run succeeds for every-other-token 4.2.0.

- .github/workflows/release.yml builds Linux x86_64, macOS arm64/x86_64 and
  Windows x86_64 binaries on a vX.Y.Z tag and attaches them with SHA-256
  checksums to a GitHub Release. No crates.io publish step.
- CHANGELOG: 4.2.0 section covering the fixes since 4.1.2.
- README install section points at the prebuilt binaries.
- CONTRIBUTING: real commands (cargo test is what CI runs; clippy -D warnings
  is not enforced because the codebase has existing warnings), no-key demo,
  release steps.
@Mattbusel
Mattbusel merged commit a5ada52 into main Sep 25, 2026
9 checks passed
@Mattbusel
Mattbusel deleted the release/4.2.0 branch September 25, 2026 19:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant