Ben Brandt 21d24f9e8b ci: build the executables with the latest Bun (#1526) ...

Follow-up to #1524. The last commit on that branch didn't make it into
the merge.

- `binaries.yml` installs `bun-version: latest` instead of pinning
`1.4.4`. The compiled executable contains the Bun runtime, so the pin
also fixed the runtime we ship. But nothing checks for new Bun releases,
so the pin would just go stale. Each build is smoke-tested on its own
platform before it uploads, so a Bun release that breaks the executable
fails that job instead of shipping. npm is unaffected, and a re-run
fixes it once Bun does. If a Bun version ever regresses past the smoke
test, we pin it then.
- Each build job writes `Built <target> with Bun x.y.z` to its step
summary, so it's visible which Bun built each release's archives.
- Re-wraps an overlong line in the file's header comment.

`ci:` because nothing published changes until the next release builds
with it.

2026-11-04 12:50:03 +00:00

..

binaries.yml

ci: build the executables with the latest Bun (#1526)

2026-11-04 12:50:03 +00:00

ci.yml

feat: ship single-file executables built with bun (#1524)

2026-11-04 11:00:25 +00:00

conventional-prs.yml

ci: validate PR titles against release-please conventions (#962)

2026-08-05 19:03:29 +02:00

publish.yml

feat: ship single-file executables built with bun (#1524)

2026-11-04 11:00:25 +00:00