fix(dev): set default-run so cargo run resolves to bunyip-api #87

Merged

longjacksonle merged 1 commit from fix/bunyip-api-default-run into main

2026-06-10 00:53:14 +02:00

longjacksonle commented

2026-06-10 00:47:43 +02:00

Owner

What

Set default-run = "bunyip-api" in bunyip-api/Cargo.toml.

Why

bunyip-api ships two binaries (bunyip-api and bunyip-e2e-bootstrap, added for the Playwright suite), so a bare cargo run -p bunyip-api is ambiguous and exits with "could not determine which binary to run". The dev container runs cargo watch -x 'run -p bunyip-api', so once the e2e binary landed the watch loop fails to launch the server on every rebuild - taking down just dev / the dev SSO stack. (Hit this live while redeploying the dev bunyip.)

Pinning the default makes cargo run resolve to the server. The e2e bootstrap is still runnable explicitly via cargo run --bin bunyip-e2e-bootstrap.

Verification

Dev container's cargo watch rebuilt and the API came up (API listening on http://0.0.0.0:4401) after the change.

🤖 Generated with Claude Code

## What Set `default-run = "bunyip-api"` in `bunyip-api/Cargo.toml`. ## Why `bunyip-api` ships two binaries (`bunyip-api` and `bunyip-e2e-bootstrap`, added for the Playwright suite), so a bare `cargo run -p bunyip-api` is ambiguous and exits with *"could not determine which binary to run"*. The dev container runs `cargo watch -x 'run -p bunyip-api'`, so once the e2e binary landed the watch loop fails to launch the server on every rebuild - taking down `just dev` / the dev SSO stack. (Hit this live while redeploying the dev bunyip.) Pinning the default makes `cargo run` resolve to the server. The e2e bootstrap is still runnable explicitly via `cargo run --bin bunyip-e2e-bootstrap`. ## Verification Dev container's `cargo watch` rebuilt and the API came up (`API listening on http://0.0.0.0:4401`) after the change. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

longjacksonle added 1 commit

2026-06-10 00:47:43 +02:00

fix(dev): set default-run so cargo run resolves to the bunyip-api server

Check / fmt / clippy / build / test (pull_request) Successful in 1m8s

Details

Create release / Create release from merged PR (pull_request) Has been skipped

Details

9caf17cc30

bunyip-api ships two binaries (bunyip-api and the bunyip-e2e-bootstrap added for the Playwright suite), which makes a bare `cargo run -p bunyip-api` ambiguous: it exits with "could not determine which binary to run". The dev container runs `cargo watch -x 'run -p bunyip-api'`, so after the e2e binary landed the watch loop fails to launch the server on every rebuild, taking down `just dev` / the dev SSO stack.

Pin `default-run = "bunyip-api"` in the package manifest so `cargo run` resolves to the server binary. The e2e bootstrap is still runnable explicitly via `cargo run --bin bunyip-e2e-bootstrap`.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>