ci: run go + web test suites on every PR#37
Merged
Merged
Conversation
…ate) Until now CI only ran on tags (release.yml), so the Go↔JS vector parity invariant was enforced only by hand. This adds a `test` workflow on pull_request + push to main: go (gofmt, vet, go test ./...) and web (npm ci, npm test). Together they are the cross-language gate — a drift in either testdata/ vector fails the build. Also gofmt-fixes two pre-existing test files (noise/pairing interop_test.go, whitespace only) so the gofmt step starts green. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
CI only ran on tags (
release.yml), so the byte-identical Go↔JS crypto gate (thetestdata/vectors) was enforced only by hand. This adds atestworkflow onpull_request+ push tomain:go vet ./...,go test ./...npm ci,npm testTogether they are the cross-language gate:
go testwrites/asserts thetestdata/vectors andnpm testasserts the JS side matches the same committed vectors. A drift on either side fails the build.Also gofmt-fixes two pre-existing test files (
noise/,pairing/interop_test.go, whitespace only) so the gofmt step starts green.Test Plan
gofmt -l go/clean;go vet ./...+go test ./...green locallynpm test82/82 locallytestrun goes green (first execution of the workflow)🤖 Generated with Claude Code