Repository navigation
Release-bound dependency resolution and native provenance for onnxruntime-win-x64 1.29.0 CPU package #33665
Replies: 1 comment
|
On the four questions, in order.
If the project wants release-bound provenance going forward, that would be a feature request, publishing a vcpkg installed-tree manifest or SLSA provenance with the releases, rather than something answerable from the existing artifacts. |
Uh oh!
There was an error while loading. Please reload this page.
Hello, I am looking for public producer/dependency material for the exact Windows x64 CPU release package:
https://github.com/microsoft/onnxruntime/releases/tag/v1.29.0
onnxruntime-win-x64-1.29.0.zip SHA-256:
c9b4b7086b529ad814f428c1bad028e20a25d7dc0699836775faace4ab5b78b2
GIT_COMMIT_ID: 2e2543f
onnxruntime.dll SHA-256:
69d8e6d3879a3b4001cdc74c8ed9ccc7e7f799a5b847059738323404519ec471
onnxruntime_providers_shared.dll SHA-256:
87f6878cdc1f80b3a9afa5b0c84663315030b4957f5bbb6b66470557cb2f48d8
The existing paired PDB source records contain no source checksums. The source-tree dependency declarations and vcpkg baseline/overrides do not by themselves prove what this historical build actually resolved. For example, the baseline FlatBuffers version and the project override differ, so I have kept them separate rather than guessing an effective version.
Could you point me to:
The fixed commit's public checks identify Azure build 1354516 / Windows CPU x64 packaging job 6c6a898f-bbbb-5c72-8695-82b606149fa2. I have not assumed this task produced the above digests without an artifact binding. The previously requested build/artifact/timeline endpoints redirected to sign-in; I am asking for public materials, not access credentials or bypassing authentication.
No application source, private PDB paths, user data or legal/commercial-use approval request is attached. Thank you.
All reactions