Skip to content

chore: bump envector-go-sdk to v0.1.3#71

Merged
jh-lee-cryptolab merged 1 commit into
mainfrom
issue-go-sdk-013
Jun 8, 2026
Merged

chore: bump envector-go-sdk to v0.1.3#71
jh-lee-cryptolab merged 1 commit into
mainfrom
issue-go-sdk-013

Conversation

@jh-lee-cryptolab

Copy link
Copy Markdown
Contributor

Context

After the Go-migration merge to main, go.mod/go.sum were left out of tidy sync, breaking CI. Pinning the SDK to a clean v0.1.3 tag and re-tidying fixes it.

TL;DR

Bump envector-go-sdk v0.1.0 → v0.1.3 and re-tidy so CI builds green.

Summary

  • Bump github.com/CryptoLabInc/envector-go-sdk v0.1.0 → v0.1.3 in vault/go.mod
  • go mod tidy: records v0.1.3's transitive deps and fixes a stale indirect→direct classification for buf.build/go/protovalidate
  • CI builds from vault/go.mod, so it now uses v0.1.3 automatically — no workflow pin to change

Alternatives

  • Hand-edit go.sum hashes only — rejected; tidy is the authoritative, reproducible path

Test plan

  • mise run check (gofmt + vet + race unit tests) passes locally
  • CI green on this PR

Update the SDK dependency from v0.1.0 to v0.1.3 and run `go mod tidy`,
which also corrects a stale indirect/direct classification for
buf.build/go/protovalidate. This realigns go.mod/go.sum so CI builds
against v0.1.3.
@jh-lee-cryptolab jh-lee-cryptolab merged commit 5e0507f into main Jun 8, 2026
1 check passed
@jh-lee-cryptolab jh-lee-cryptolab deleted the issue-go-sdk-013 branch June 8, 2026 04:56
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