v0.8.0

Added

• bacon.toml as a runner task source. Jobs surface in runner list /
  runner info, dispatch via runner run <job> / run <job>, and resolve
  under the bacon.toml:<job> qualified syntax. Bacon is detected as a
  task runner alongside just / make / go-task. Jobs whose names start with
  _ are treated as private and hidden. When the bacon CLI is on
  PATH, extraction shells out to bacon --list-jobs so bacon's built-in
  jobs (check, clippy, test, …) merge into the listing alongside
  whatever bacon.toml declares — same view bacon itself presents. Falls
  back to TOML parsing when bacon isn't installed. Job arguments forward
  through bacon's -- separator (runner run test -- --ignored →
  bacon test -- --ignored) so they reach the underlying job intact.
• Project-local bacon.toml defining lint, test-all, and bins jobs
  for the runner crate, mirroring the cargo l / cargo t aliases.
• cargo binstall runner-run support via [package.metadata.binstall] in
  Cargo.toml. cargo-binstall now downloads the prebuilt binary from the
  matching GitHub release asset (runner-v{version}-{target}.tar.gz)
  instead of building from source — same archives
  taiki-e/upload-rust-binary-action uploads from release.yml. Both
  runner and run install side by side, no toolchain required.

Changed

• Release pipeline reordered. crates-release now triggers on push: tags: ['v*'] instead of release: published, so cargo publish
  fires in parallel with binary builds and no longer waits on the npm
  publish chain to complete first. release.yml gains a final
  publish-release job that flips the draft GitHub release to
  published once binaries and the npm-dist artifact land — this is
  now the natural pivot of the release lifecycle and drives
  npm-release.yml via release: published. npm-release.yml
  drops its workflow_run trigger (and the draft-flip side job that
  was hidden in it), resolving the build run-id for cross-workflow
  artifact download via gh run list instead. Net effect: tag push
  alone ships crates.io immediately, and the GH release auto-publishes
  once binaries are ready — no more manual draft-flipping.
• npm/facade/README.md updates the install fallback instructions to
  cargo install runner-run (crates.io) instead of the git-source
  form, matching the 0.7.1 README/landing-page change.
• npm/facade/package.json template no longer carries a version
  field. The build script (npm/scripts/build-packages.ts) injects
  the version from cargo metadata at build time and the template
  value was always overwritten. Single source of truth is now
  Cargo.toml.

Fixed

• runner completions $SHELL no longer fails when $SHELL expands to a
  full path (e.g. /usr/bin/zsh). The explicit <shell> arg now accepts
  either a bare name (zsh) or a full path, mirroring the bare-arg
  fallback that already file-stems $SHELL. Previously the stock clap
  ValueEnum parser rejected anything but the bare names, making the
  explicit and implicit paths inconsistent.
• pwsh surfaces in runner completions --help and the rejection error
  alongside powershell. The internal mapping has accepted both since
  shell_from_path was written; only the user-facing message lagged.

What's Changed

• feat(bacon): add bacon.toml as task source by @kjanat in #15
• feat(binstall): add cargo-binstall metadata by @kjanat in #17

Full Changelog: v0.7.1...v0.8.0