[Web] Bump tvmjs version to 0.26.0 and apache-tvm-ffi floor to >=0.1.13.post2 - #20093
Merged
spectrometerHBH merged 2 commits intoAug 5, 2026
Merged
Conversation
MasterJH5574
changed the title
This was referenced Aug 5, 2026
spectrometerHBH
approved these changes
Aug 5, 2026
tlopex
pushed a commit
that referenced
this pull request
Aug 5, 2026
The `v0.26.0` release branch has been cut and `main` now carries the `v0.27.dev0` tag, so this opens the matching npm dev cycle. `web/package.json` is the only version that `setuptools_scm` does not derive from git tags — npm is a separate ecosystem — so it is bumped by hand once per cycle. The release branch keeps `0.26.0` for the v0.26.0 release (#20093). Note for the release timeline: while v0.26.0 is still in flight, any cherry-pick from `main` to the release branch that touches `web/package*` will conflict with this bump, so it may be preferable to hold the merge until v0.26.0 has shipped.
tqchen
pushed a commit
that referenced
this pull request
Aug 5, 2026
The bundled `3rdparty/tvm-ffi` gitlink is at `v0.1.13-post2` (#20088), so TVM compiles against post2 headers. The wheel does not bundle `libtvm_ffi.so` — it is excluded from the auditwheel, delocate and delvewheel repair commands in `pyproject.toml` — so the runtime library is whatever the `apache-tvm-ffi` dependency resolves to at install time. That makes this floor an ABI contract rather than a formality. `ModuleObj::GetFunction` changed from `virtual Function` to `virtual Optional<Function>` between `0.1.13` and `0.1.13.post2` (apache/tvm-ffi#700, apache/tvm-ffi#701). That is a C++ vtable boundary whose mangled symbol does not encode the return type, so pairing a post2-compiled TVM with an older `libtvm_ffi.so` fails silently rather than at link time, and there is no runtime version guard that would catch it. A plain `pip install` already resolves to post2 since pip picks the newest match, so this is latent rather than universal; raising the floor closes the pinned and constrained resolves that `>=0.1.13` still permits. The same bump is included in #20093 for the v0.26.0 release branch.
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.
Bumping the tvmjs version from
0.26.0-dev0to0.26.0for v0.26.0 release.Also bumping the apache-tvm-ffi floor given the v0.13.0.post2 comes with abi breaking changes.