Bump Microsoft.ML.OnnxRuntime from 1.27.1 to 1.28.0 - #1059
Conversation
--- updated-dependencies: - dependency-name: Microsoft.ML.OnnxRuntime dependency-version: 1.28.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
|
Codex review: needs maintainer review before merge. Reviewed July 27, 2026, 2:16 AM ET / 06:16 UTC. ClawSweeper reviewWhat this changesUpdates the shared speech-transcription dependency Microsoft.ML.OnnxRuntime, the native ONNX model inference engine used alongside Whisper.net, from 1.27.1 to 1.28.0. Merge readinessKeep this fresh Dependabot PR open for normal dependency review. It makes a one-line direct production package update, but the repository-required build and shared/tray test validation is not yet evidenced in the PR context and the upstream minor release changes the native inference runtime. Priority: P2 Review scores
Verification
How this fits togetherOpenClaw's shared library supplies speech-transcription capabilities used by Windows-node and tray-adjacent workflows. Audio/model inference flows through Whisper.net into Microsoft.ML.OnnxRuntime, which loads and executes the native ONNX runtime before returning transcription results to higher-level features. flowchart LR
A[Audio or speech input] --> B[Whisper.net transcription]
B --> C[Shared OpenClaw library]
C --> D[ONNX Runtime package]
D --> E[Native model inference]
E --> F[Transcribed result for node and tray flows]
Before merge
Agent review detailsSecurityNone. Review metrics
Merge-risk optionsMaintainer options:
Copy recommended automerge instructionTechnical reviewBest possible solution: Merge the narrow package update only after the required build, shared tests, and tray tests pass on the proposed head, with any ONNX or Whisper runtime failure investigated as an upgrade-compatibility regression. Do we have a high-confidence way to reproduce the issue? Not applicable: this PR updates a dependency version rather than reporting an existing product failure. Compatibility validation is still needed on the supported transcription/runtime path. Is this the best way to solve the issue? Unclear: changing the existing direct PackageReference is the narrowest implementation, but the best merge decision depends on the required build and test evidence for the updated native runtime. AGENTS.md: found and applied where relevant. Codex review notes: model internal, reasoning high; reviewed against acf4ab1d2b02. LabelsLabel changes:
Label justifications:
EvidenceWhat I checked:
Likely related people:
Rank-up movesOptional improvements that raise the rating; they are not merge blockers.
Rating scale
Overall follows the weaker of proof and patch quality. Workflow
|
Updated Microsoft.ML.OnnxRuntime from 1.27.1 to 1.28.0.
Release notes
Sourced from Microsoft.ML.OnnxRuntime's releases.
1.28.0
Announcements & Breaking Changes
nvrtcis no longer linked, which significantly reduces the required CUDA redistributable footprint (#29252, #29808, #29705, #29620).OrtModelPackageApinow lives in the experimental C API and may change in future releases (#28746, #29142, #28990).wgsl-genimplementation (#29141, #28355).CUDA_QUANT_PREPROCESSis off by default (#29687).Security Fixes
Memory safety & input validation
bind_inputcausing an out-of-bounds write (#28839)TensorAtfor sub-byte packed types (#28973)Col2Iminputs to prevent heap over-read (#28706)CropAndResizeagainst malformedcrop_sizetensors (#28766)BeamSearchvocab_sizeagainst logits width (#28774)WhisperDecoderSubgraph::CreateInitialFeeds(#29239)SparseAttentionCSR indices/key lengths and rejected zero-dimensionblock_row_indices(#29015, #29242)mask_indexto valid bounds (#29449)MaxpoolWithMaskkernel rank against input spatial rank (#29253)EmbedLayerNorm/SkipLayerNormshapes exceeding 32-bit output indexing (#29264)DecoderAttention/MultiHeadAttentionshape inference and negative-axis handling inExpandDimsshape inference (#29268, #29448)TreeEnsembletarget id validation and added input validation toLinearClassifier(#29293, #29060)DynamicQuantizeLSTMzero-point/scale validation typos (#29462)Loop/Scanoutput concatenation (#29397)raw_datato{0, 1}on unpack (#29238)Resize,PadFusion, and LoRA handling (#28779, #28780, #28801)WithOutputTensorin the Rust bindings (#29251)Integer overflow & allocation size
MlasConvPrepareworking-buffer products andConvTransposepad computation with SafeInt (#29444, #29446)SamplingState::Initthat could cause a heap buffer overflow (#29443)B/scales/zero-points shape inMatMulNBits::PrePack(#29445)ConstantOfShapeoutput size against the input initializer before constant folding (#28751)Pad(int64/int32 truncation),Slice, andGatherBlockQuantized(#28721, #28704, #28718)Supply chain & tooling
... (truncated)
Commits viewable in compare view.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)