Peter Schilling 12860b253c ci: pin deno to 2.7.9 in the release and publish pipelines ...

027f25e pinned deno to 2.7.9 in mise.toml and ci.yaml, but the two workflows
that actually build and ship artifacts were left on 'v2.x': release.yml runs
'deno compile' for every target triple, and publish.yaml runs codegen before
'jsr publish'. So the binaries users install were produced by whatever v2.x
resolved to at build time, not the toolchain the project pins and tests on.

build-setup.yml is the dist 'github-build-setup' hook that generates the deno
step in release.yml, so it and the generated line are updated together to keep
'dist generate' a no-op.

setup-deno@v2 already runs an exact 2.7.9 in both ci.yaml jobs, so this is the
version resolution those jobs have been proving all along.

2026-07-14 22:10:47 -07:00

..

ci.yaml

fix(test): skip keyring integration test when the macOS keychain is locked

2026-07-14 22:10:09 -07:00

publish.yaml

ci: pin deno to 2.7.9 in the release and publish pipelines

2026-07-14 22:10:47 -07:00

release.yml

ci: pin deno to 2.7.9 in the release and publish pipelines

2026-07-14 22:10:47 -07:00