Skip to content

go: full-module CI gate + fix stale probe (Phase 6 hardening) - #22

Merged
zarah-s merged 1 commit into
mainfrom
go-sdk-phase6-hardening
Jul 30, 2026
Merged

go: full-module CI gate + fix stale probe (Phase 6 hardening)#22
zarah-s merged 1 commit into
mainfrom
go-sdk-phase6-hardening

Conversation

@zarah-s

@zarah-s zarah-s commented Jul 30, 2026

Copy link
Copy Markdown
Member

Hardens the Go host module before its next release.

  • Fix the import-purity probe (Instantiate now returns 3 values, probe assigned 2 → root test suite was red).
  • CI gated only ./child; now gates the whole module (gofmt + go vet ./... + go test ./...). This is why alpha.12 shipped with a red root test.

Local gate green: gofmt clean, vet clean, go test ./... passes.

Two coupled fixes that harden the Go host module for release:

- The import-purity probe still destructured Instantiate() into 2 values,
  but the factory API returns 3 (Address, []byte, int32) — so the probe
  failed to tinygo-build and the root-package test suite was red. Updated
  the probe to the current signature.

- CI only ran `go test ./child`, never the root package, so that red test
  (and the borsh conformance/parity + u128 suites) never gated a release —
  which is how a broken probe shipped in alpha.12. The Go job now runs
  gofmt + `go vet ./...` + `go test ./...` over the whole module (tinygo
  is already installed in that job, so the import-purity test runs).
@zarah-s
zarah-s merged commit 8cf88f5 into main Jul 30, 2026
0 of 5 checks passed
@zarah-s
zarah-s deleted the go-sdk-phase6-hardening branch July 30, 2026 18:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant