Matthew Jackson
d3c58791ff
Tests, crates.io publish, and the GitHub Release no longer serialize behind each other: each job only needs the version-check (verify) gate. Binary consumers git-tag-pin libfreemkv, so they start building the instant the tag exists rather than waiting on the crates.io publish. crates.io publish runs as an independent job for external consumers and uses --no-verify (CI already compiled this commit in the test job).
72 lines
2.6 KiB
YAML
72 lines
2.6 KiB
YAML
name: Release
|
|
|
|
on:
|
|
push:
|
|
tags:
|
|
- 'v*'
|
|
|
|
permissions:
|
|
contents: write
|
|
|
|
jobs:
|
|
verify:
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- uses: actions/checkout@v5
|
|
- name: Verify Cargo.toml version matches tag
|
|
run: |
|
|
CARGO_VER="v$(grep '^version' Cargo.toml | head -1 | sed 's/.*"\(.*\)"/\1/')"
|
|
if [ "$CARGO_VER" != "${{ github.ref_name }}" ]; then
|
|
echo "::error::Cargo.toml says $CARGO_VER but tag is ${{ github.ref_name }}"
|
|
exit 1
|
|
fi
|
|
echo "Version match: $CARGO_VER"
|
|
|
|
# Tests run as a PARALLEL TRIPWIRE: they fail the run if they fail, but the
|
|
# publish/release jobs do NOT `needs:` this job. The tag decision was already
|
|
# gated by the local precommit (same Rust 1.86, same commit). Binary consumers
|
|
# (freemkv/autorip/bdemu) git-tag-pin libfreemkv and therefore start building
|
|
# the instant this tag exists — so this test job and the crates.io publish
|
|
# below must NOT sit on their critical path.
|
|
test:
|
|
needs: verify
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- uses: actions/checkout@v5
|
|
- uses: dtolnay/rust-toolchain@1.86.0
|
|
# libfreemkv is a library — Cargo.lock isn't tracked, so --locked
|
|
# would always fail (no lockfile to lock against on a fresh runner).
|
|
- run: cargo test
|
|
|
|
# crates.io publish is an INDEPENDENT job: it serves EXTERNAL consumers only.
|
|
# The freemkv binaries no longer depend on it (they git-tag-pin libfreemkv via
|
|
# a committed [patch.crates-io]), so this publish runs in parallel with their
|
|
# release builds rather than gating them. It only `needs: verify` (the version
|
|
# check) — NOT `test` — so publish isn't serialized behind the test suite.
|
|
publish:
|
|
needs: verify
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- uses: actions/checkout@v5
|
|
- uses: dtolnay/rust-toolchain@1.86.0
|
|
# --no-verify: CI already compiled this exact commit (in the `test` job
|
|
# and on every push via ci.yml). cargo publish's default re-verify does a
|
|
# full cold release build of the packaged tarball, which here is pure
|
|
# redundant work (~a cold lib build). Skip it.
|
|
- name: Publish to crates.io
|
|
run: cargo publish --no-verify
|
|
env:
|
|
CARGO_REGISTRY_TOKEN: ${{ secrets.CARGO_REGISTRY_TOKEN }}
|
|
|
|
release:
|
|
# Only needs `verify`; the GitHub Release can be cut as soon as the version
|
|
# check passes, in parallel with test + publish.
|
|
needs: verify
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- uses: actions/checkout@v5
|
|
- name: Create GitHub Release
|
|
uses: softprops/action-gh-release@v2
|
|
with:
|
|
generate_release_notes: true
|