Skip to content

chore(deps): bump zvec submodule to v0.8.0 - #19

Merged
chinaux merged 1 commit into
mainfrom
chore/zvec-v0.8.0
Oct 21, 2026
Merged

chinaux merged 1 commit into
mainfrom
chore/zvec-v0.8.0

Conversation

@chinaux

@chinaux chinaux commented Oct 21, 2026

Copy link
Copy Markdown
Collaborator

What

Moves the zvec submodule off v0.8.0-beta2 (8397071) onto the final upstream v0.8.0 tag (7b75327).

Submodule zvec 8397071..7b75327:
  > docs: update README highlights for v0.8.0 (#829)

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:

 README.md    | 25 +++++++++++++------------
 README_CN.md | 28 ++++++++++++++++------------
 2 files changed, 29 insertions(+), 24 deletions(-)

src/include/zvec/c_api.h is byte-identical between v0.8.0-beta2 and v0.8.0, so:

  • no Go binding changes are needed (neither cgo nor purego),
  • the purego ABI requirement stays at 0.8 (purego_loader.go),
  • the already-published v0.8.0 release 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 printed v0.8.0-beta2 (0.8.0) in CI logs and now prints v0.8.0 (0.8.0).

Verification

  • git -C zvec diff v0.8.0-beta2 v0.8.0 -- src/include/zvec/c_api.h → empty
  • make check-zvec (sync-zvec.sh --check-only) → no C-API header changes between 7b75327 and upstream main (8d49969), so tracking the release tag costs nothing
  • Local vendor mode: go build . ./cmd/... ./examples/... OK, go test -tags integration -short . OK
  • Local purego mode: CGO_ENABLED=0 ZVEC_LIBRARY_PATH=lib/darwin_arm64/libzvec_c_api.dylib go test -tags integration -short -run Purego . OK
  • go vet . ./cmd/... clean
  • CI will rebuild the C-API from the new submodule commit on all six platforms

Single-file change (the gitlink); no .go, workflow or doc files touched.

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).
@chinaux
chinaux merged commit b995784 into main Oct 21, 2026
12 checks passed
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