Repository navigation
evalhub 0.1.2
Release from the tag: crates, image and GitHub Release by one workflow (0.1.2) (#15)
The tag push becomes the only release action a person takes; the release workflow does the rest.
What changes
.github/workflows/release.ymlon av*tag:check: the tag names the version inCargo.tomland the tagged commit is onmain; otherwise nothing runs.crates:just package,cargo semver-checksagainst the versions on crates.io, thencargo publishfor whichever ofevalhub-schema/evalhub-core/evalhub-queryis not yet on crates.io at that version. Authentication is crates.io Trusted Publishing (OIDC,rust-lang/crates-io-auth-action); no token is stored. A rerun publishes nothing twice.image: as before (ghcr.io/ynishi/evalhub:<version>,:latest).release: a GitHub Release for the tag, notes from the merged pull request's body plus crate and image links.
deploy/release/land.sh <pr> <issue>: merge with a merge commit (never squash), close the issue, fast-forwardmain, thentag.sh.deploy/release/tag.sh: onmain, clean, HEAD isorigin/main, CI for HEAD green (waits), version fromCargo.toml, tag once, push, follow the workflow withgh run watch.just semver-check; CONTRIBUTING §Releases; pointers in AGENTS.md anddocs/hosting.md.
Why not release-plz (dsl-kit's flow)
Its version and changelog are computed from Conventional Commit headers, which this repository does not use (prose subjects, bump riding with the last change), and its release PR carries a bot commit without Signed-off-by. What it is for (no hand-typed publish, one tag as the trigger, a semver check, a release page) is taken; the rest is left.
0.1.2
This PR is the release that exercises the workflow it adds: the version bump rides in its one commit, and landing it (deploy/release/land.sh 15 14) tags v0.1.2 from a commit that contains release.yml. No Rust code changed since 0.1.1.
Verified
bash -non both scripts;release.ymlparses; the PR lookup by merge sha returns #13 for the 0.1.1 merge commit;gh run watch --exit-statusexists.cargo fmt --check,cargo clippy --workspace --all-targets -D warnings,cargo test -p evalhub-schema / -core / -query,just packageat 0.1.2,just semver-checkagainst 0.1.1.- Trusted Publishing is enabled on crates.io for the three crates (repository
ynishi/evalhub, workflowrelease.yml). - Not run before merge: the workflow itself; that is what the tag does.
Refs #14
SDK crates: evalhub-schema evalhub-core evalhub-query
Image: ghcr.io/ynishi/evalhub:0.1.2