Repository navigation
Conversation
…opy is gone github.com/microsoft/onnxruntime answers 404 since 17.11.2026 (repo, API and every release download), so `models download` could not install the native library on Linux and macOS and the models fell back to WebAssembly. The Native runtime CI job failed on every PR. The library now comes from Microsoft's NuGet package Microsoft.ML.OnnxRuntime 1.30.0. One HTTP Range request fetches only the deflated bytes of this system's library out of the 157 MB zip; installFiles checks the slice's size and sha256, fflate inflates it, and the library's own sha256 is checked as before. A published NuGet version never changes, and the package signature nuget.org may replace is the zip's last file, so the pinned offsets hold. - linux-x64, linux-arm64: the same library bytes as the GitHub release. - darwin-arm64: NuGet's own build of 1.30.0, same size and install name (@rpath/libonnxruntime.1.dylib), new sha256. - Windows keeps onnxruntime-node's npm tarball. ModelFile gains an optional `offset`, sent as a Range header. The package's probe-native.mjs takes the same slices. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…packages The owner wants no run-time dependency on Microsoft's hosting, GitHub or NuGet. The library now comes from @wirecat/onnxruntime-<platform> on registry.npmjs.org, one package per platform (linux-x64, linux-arm64, darwin-arm64, win32-x64, win32-arm64), each holding only that library plus Microsoft's LICENSE and ThirdPartyNotices.txt, with os/cpu set. `models download` still fetches on demand into the shared models folder, through the existing tarball path (installFiles, gunzip, tarMember): every NATIVE entry now has the same shape, member `package/<library>`. Tarball and library sha256 are both pinned. The NuGet Range code from the previous commit is reverted: nothing needs it. bin/publish-onnxruntime builds the packages once from the NuGet 1.30.0 nupkg (Linux, macOS) and the onnxruntime-node 1.30.0 tarball (Windows, DirectML build, same DLL sha as today), packs them with npm pack (reproducible here: two runs, same sha256), refuses any tarball that differs from the pin, and with --publish publishes those not yet on npm. Not published: a new npm package needs the owner. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
leemour
marked this pull request as draft
November 18, 2026 18:09
This branch has not been deployed
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.
Task
Restore the native ONNX Runtime on Linux and macOS without any run-time dependency on Microsoft's hosting (owner's direction). Do not merge before the five packages are on npm: the "Native runtime" job downloads them and fails with 404 until then.
Why
Since about 22:20 UTC on 17.11.2026,
github.com/microsoft/onnxruntimeanswers 404: the repository, the API and every release download (runtimewire).models downloadcould not install the native library on Linux and macOS, so the models ran through WebAssembly. The "Native runtime" job failed on every PR.What
@wirecat/onnxruntime-{linux-x64,linux-arm64,darwin-arm64,win32-x64,win32-arm64}1.30.0. Each holds only that library, plus Microsoft'sLICENSE(MIT) andThirdPartyNotices.txtfrom the nupkg, and setsos/cpu. Each README records the source URL, the source sha256 and the library sha256.npmTarballused:installFiles→ gunzip →tarMember), with memberpackage/<library>. The tarball and the library sha256 are both pinned. No new download code.bin/publish-onnxruntime: one Node file. It downloads the NuGetMicrosoft.ML.OnnxRuntime1.30.0 nupkg (its SHA-512 matches NuGet's catalog) and theonnxruntime-node1.30.0 tarball, checks both, and builds and packs the five packages intopackages/onnxruntime/(git-ignored). It refuses any tarball whose sha256 differs from the pin;npm packgave the same bytes on two runs. With--publish, it publishes the packages that are not on npm yet. The npm token comes from the keyring.@rpath/libonnxruntime.1.dylib, new sha256bffaa6ef…6879. Windows fromonnxruntime-nodeas before (the DirectML ordinal), the same DLL sha.packages/onnx/probe-native.mjs(monthly ONNX workflow) takes the same packages.Testing
downloadTextModel("e5-small")(whatmodels downloadruns) installs fromonnxruntime-linux-x64-1.30.0.tgz, andonnxRuntime().nativeistrue. 64 passages embed in 272–292 ms native against 669 ms through WebAssembly.onnx-runtime.native.test.tswithNATIVE_RUNTIME_CHECK=nativepasses the same way.npm publish --dry-runof a packed tarball. typecheck, lint, docs:check, and the unit tests for embeddings, speech and model-downloads.🤖 Generated with Claude Code