Skip to content

ci: give apiCheck its own named PR leg #1176

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
michalharakal merged 1 commit into from
Aug 26, 2026
Merged

ci: give apiCheck its own named PR leg #1176

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions .github/workflows/build.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,13 +54,17 @@ jobs:
tasks: testAndroidHostTest
# golden-parity: the SKEEP-003 packed-encoding gate (#1005). Bit-identical decode /
# scalar-kernel / TurboQuant digests on JVM and Kotlin/Native plus the dispatch parity
# tests, and the binary-compatibility check (apiCheck) that the contributing docs require
# but the per-target test legs do not run. Fast (a few minutes) so it fails early.
# tests. Fast (a few minutes) so it fails early.
- name: golden-parity
tasks: >-
apiCheck
:skainet-backends:skainet-backend-cpu:jvmTest --tests sk.ainet.exec.golden.*
:skainet-backends:skainet-backend-cpu:linuxX64Test --tests sk.ainet.exec.golden.*
# api-compatibility: the binary-compatibility check the contributing docs require but the
# per-target test legs do not run. Its own leg — not folded into golden-parity — so a
# stale api dump reads as "api-compatibility ✘" instead of a red parity leg nobody
# associates with dumps (#1171 merged a stale dump exactly that way; #1174 repaired it).
- name: api-compatibility
tasks: apiCheck

permissions:
contents: read
Expand Down
Loading