Skip to content

evalhub 0.1.2

Choose a tag to compare

@github-actions github-actions released this 22 Sep 11:01
· 43 commits to main since this release
98d39c6

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.yml on a v* tag:
    • check: the tag names the version in Cargo.toml and the tagged commit is on main; otherwise nothing runs.
    • crates: just package, cargo semver-checks against the versions on crates.io, then cargo publish for whichever of evalhub-schema / evalhub-core / evalhub-query is 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-forward main, then tag.sh.
  • deploy/release/tag.sh: on main, clean, HEAD is origin/main, CI for HEAD green (waits), version from Cargo.toml, tag once, push, follow the workflow with gh run watch.
  • just semver-check; CONTRIBUTING §Releases; pointers in AGENTS.md and docs/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 -n on both scripts; release.yml parses; the PR lookup by merge sha returns #13 for the 0.1.1 merge commit; gh run watch --exit-status exists.
  • cargo fmt --check, cargo clippy --workspace --all-targets -D warnings, cargo test -p evalhub-schema / -core / -query, just package at 0.1.2, just semver-check against 0.1.1.
  • Trusted Publishing is enabled on crates.io for the three crates (repository ynishi/evalhub, workflow release.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