fix: pin Bun setup action supported by Gitea runner
All checks were successful
Mostovik Backend CI/CD / Tests and lint (push) Successful in 4m48s
Mostovik Backend CI/CD / Build linux/amd64 release images (push) Successful in 2m59s
Mostovik Backend CI/CD / Deploy and verify internal main (push) Has been skipped
Mostovik Backend CI/CD / Deploy dev (push) Successful in 2m23s

This commit is contained in:
Aleksandr Meshchryakov
2026-10-05 18:34:06 +02:00
parent af02d1ce8a
commit 0dd763109b
2 changed files with 4 additions and 1 deletions

View File

@@ -39,7 +39,7 @@ jobs:
node-version: 24 node-version: 24
- name: Setup contract toolchain - name: Setup contract toolchain
uses: oven-sh/setup-bun@v2 uses: oven-sh/setup-bun@f4d14e03ff726c06358e5557344e1da148b56cf7 # v1, node20 action runtime
with: with:
bun-version: 1.3.9 bun-version: 1.3.9

View File

@@ -43,6 +43,9 @@ raw keys. Ordinary pytest runs write no fixture file; writing is enabled only by
used. The generated validators are disposable build output, never handwritten. used. The generated validators are disposable build output, never handwritten.
Bun is pinned to 1.3.9 in CI; the tool dependencies are locked in `bun.lock`. Bun is pinned to 1.3.9 in CI; the tool dependencies are locked in `bun.lock`.
The setup action is pinned to `oven-sh/setup-bun@f4d14e03ff726c06358e5557344e1da148b56cf7`
(v1, Node 20 action runtime): the current Gitea runner rejects the v2 Node 24
action runtime before project tests. This does not change the installed Bun version.
CI regenerates the source Swagger document, runs `bun build.mjs --check`, generates CI regenerates the source Swagger document, runs `bun build.mjs --check`, generates
a client and compiles a strict TypeScript fixture. It fails if the bundled contract a client and compiles a strict TypeScript fixture. It fails if the bundled contract
is stale, invalid, loses discrimination, or removes the named ordering enum. is stale, invalid, loses discrimination, or removes the named ordering enum.