Repository navigation
chore(deps): bump zvec submodule to v0.8.0 - #19
Merged
Merged
Conversation
Upstream alibaba/zvec has published the final v0.8.0 tag, so move the submodule off v0.8.0-beta2 (8397071) onto v0.8.0 (7b75327). The two tags differ by exactly one upstream commit, "docs: update README highlights for v0.8.0 (#829)", which only touches upstream README.md and README_CN.md. src/include/zvec/c_api.h is byte-identical between them, so no Go binding changes are needed and the purego ABI requirement stays at 0.8. Bumping anyway keeps version reporting accurate: the C-API build derives its version from `git describe`, which printed "v0.8.0-beta2 (0.8.0)" and now prints "v0.8.0 (0.8.0)". scripts/sync-zvec.sh --check-only reports no C-API header changes between this commit and upstream main (8d49969).
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
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.
What
Moves the
zvecsubmodule offv0.8.0-beta2(8397071) onto the final upstreamv0.8.0tag (7b75327).Why this is a no-op for the bindings
The two tags differ by exactly one upstream commit, and it only touches upstream
README.md/README_CN.md:src/include/zvec/c_api.his byte-identical betweenv0.8.0-beta2andv0.8.0, so:0.8(purego_loader.go),v0.8.0release archives remain valid — they were built from a C-API-identical tree.Worth doing anyway for version reporting: the C-API build derives its version from
git describe, which printedv0.8.0-beta2 (0.8.0)in CI logs and now printsv0.8.0 (0.8.0).Verification
git -C zvec diff v0.8.0-beta2 v0.8.0 -- src/include/zvec/c_api.h→ emptymake check-zvec(sync-zvec.sh --check-only) → no C-API header changes between7b75327and upstreammain(8d49969), so tracking the release tag costs nothinggo build . ./cmd/... ./examples/...OK,go test -tags integration -short .OKCGO_ENABLED=0 ZVEC_LIBRARY_PATH=lib/darwin_arm64/libzvec_c_api.dylib go test -tags integration -short -run Purego .OKgo vet . ./cmd/...cleanSingle-file change (the gitlink); no
.go, workflow or doc files touched.