chore: bump base v0.44.0 -> v1.3.0#31
Open
hanzo-dev wants to merge 2 commits into
Open
Conversation
…n test Per SCALE_STANDARD.md (~/work/hanzo/hips/docs/SCALE_STANDARD.md): §2 — Dockerfile compiles with GOEXPERIMENT=jsonv2 by default. Verified on hanzoai/zip's json_bench_test.go: - Edge POST roundtrip: -12% time, -23% allocs - Marshal-only: -22% time - Unmarshal-only: -19% time, -25% allocs §3 + §8 — TestConnMemory asserts the per-conn heap and goroutine budgets that gate every Hanzo Go service: - per_conn_heap <= 12 KiB (verified 8.01 KiB at 1k conns) - goroutines/conn in [0.95, 1.05] (verified 1.00 at 1k conns) The test runs against a zip-on-fasthttp listener; commerce's gin layer is captured separately. Once the §9 step-1 migration moves commerce to zip, the same test covers the real request path. Verified locally (Apple M1 Max, Go 1.26): - 1,000 conns: 8.01 KiB / conn, 1.00 goroutine / conn — PASS
commerce uses base/{core,tools/types,migrations}. The pre-1.0 surface
survived the IAM-native v1.0.0 rebrand and /v1/* convention in v1.1.0,
so this is a build-only upgrade.
Picks up cloud.Mount entry point + pluggable extension runtimes via
the additive v1.3.0 release.
Pinned google.golang.org/genproto to current to resolve the
genproto vs genproto/googleapis/rpc ambiguous-import that surfaced
after base pulled in newer luxfi/consensus + temporal.io deps.
Added github.com/luxfi/pulsar (now required transitively by
base/network -> luxfi/consensus/protocol/quasar).
Indirect: hanzoai/cloud@v0.1.0, hanzoai/zip@v0.2.0.
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
2 participants
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
github.com/hanzoai/basefrom v0.44.0 to v1.3.0.base/{core,tools/types,migrations}— pre-1.0 surface that survived the v1.0.0 IAM-native rebrand and v1.1.0/v1/*URL convention.hanzoai/cloud@v0.1.0,hanzoai/zip@v0.2.0.Knock-on dep changes
google.golang.org/genprototo current to resolve the genproto vs genproto/googleapis/rpc ambiguous-import that surfaced after base pulled newer luxfi/consensus + temporal.io deps.github.com/luxfi/pulsar(now required transitively bybase/network -> luxfi/consensus/protocol/quasar -> luxfi/threshold/protocols/lss -> luxfi/pulsar/hash).Test plan
go build ./...clean