Update cargo dependencies (livekit-wakeword) - #1305
Conversation
Generated by renovateBot
No changeset foundThis PR modifies versioned packages but doesn't include a changeset. The following packages require a version bump:
A package must be bumped when its own files change, and whenever a package it depends on is bumped (so downstream consumers get a matching release). Click here to create a changeset for the missing packages The link pre-populates a changeset file with If this change doesn't require a version bump, add the |
| resampler = "0.5" | ||
| thiserror = "2" | ||
|
|
||
| [target.'cfg(not(all(target_arch = "aarch64", target_os = "windows", target_env = "msvc")))'.dependencies] | ||
| ort = { version = "2.0.0-rc.11", default-features = false, features = ["alternative-backend"] } | ||
| ort-tract = "0.2.0+0.22" | ||
| ort-tract = "0.3.0" |
There was a problem hiding this comment.
🟡 Dependency update ships without the required change note
The dependency version bump for the wake-word package (resampler = "0.5" at livekit-wakeword/Cargo.toml:12) is submitted without adding the change note file the project requires for every pull request, so the release tooling will not know this package needs a version bump.
Impact: The published package can be released without its dependency change being recorded or its version bumped.
Missing knope changeset entry for livekit-wakeword
AGENTS.md ("Documenting changes") states: "Every PR needs a changeset" and "Changeset must list any crates which need to be bumped stemming from the change". The repository uses knope (knope.toml) with change notes stored in /.changeset (currently fix-publisher-renegotiation-deadlock.md, fix_nvenc_dynamic_bitrate_updates.md, fix_uniffi_android_package_build.md). This commit only touches Cargo.lock and livekit-wakeword/Cargo.toml (bumping resampler 0.4→0.5 and ort-tract 0.2→0.3, plus lockfile ort rc.11→rc.12) and adds no changeset for livekit-wakeword.
Prompt for agents
AGENTS.md requires every PR to include a knope changeset in /.changeset listing crates that need a version bump. This PR bumps livekit-wakeword's dependencies (resampler 0.4->0.5, ort-tract 0.2->0.3, and ort rc.11->rc.12 in Cargo.lock) but adds no changeset. Add a changeset file (e.g. via `knope document-change`) noting a patch bump for the livekit-wakeword crate describing the dependency updates.
Was this helpful? React with 👍 or 👎 to provide feedback.
This PR contains the following updates:
2.0.0-rc.11→2.0.0-rc.122.0.0-rc.130.2.0+0.22→0.3.00.4.00.4→0.5Release Notes
pykeio/ort (ort)
v2.0.0-rc.12Compare Source
2.0.0-rc.12
💖 If you find
ortuseful, please consider sponsoring us on Open Collective 💖🤔 Need help upgrading? Ask questions in GitHub Discussions or in the pyke.io Discord server!
This release was made possible by Rime.ai!
📍 Multiversioning
The big highlight of this release is multiversioning:
ortcan now use any minor version of ONNX Runtime from v1.17 to v1.24. New features are gated behindapi-*feature flags, likeapi-20orapi-24. These flags will set the minimum version of ONNX Runtime required byort.More info 👉 https://ort.pyke.io/setup/multiversion
🪄 Automatic device selection
With ONNX Runtime 1.22 or later,
ortwill now automatically use an NPU if one is available for maximum efficiency & power savings! Setting your own execution providers will override this.This is thanks to the super cool new
SessionBuilder::with_auto_deviceAPI! There's alsoSessionBuilder::with_devicesfor finer control.👁️ CUDA 13
ortnow ships builds for both CUDA 12 & CUDA 13! It should automatically detect which CUDA you're using, but if it gets it wrong, you can override it by setting theORT_CUDA_VERSIONenvironment variable to12or13.🩹
SessionBuildererror recoveryYou can now recover from errors when building a session by calling
.recover()on the error type to get theSessionBuilderback.🛡️ Build attestations
Prebuilt binaries are now attested via GitHub Actions, so you can verify that they are untampered builds of ONNX Runtime coming straight from pyke.io.
To verify, download your binary package of choice and use the
ghCLI to verify:(Also note that the SHA-256 hash lines up with the one defined in
dist.txt.)Moving stuff around
ORT_LIB_LOCATIONenvironment variable has been renamed toORT_LIB_PATH._LOCATION.ort::tensoris now inort::value, because why have atensormodule if theTensor<T>type actually comes from thevaluemodule?IoBindingandAdapterwere moved from their own modules intoort::session. All sub-modules ofort::sessionbesidesbuilderwere collapsed intoort::session.ort::operatorwere collapsed intoort::operator.with_denormal_as_zero->with_flush_to_zerowith_device_allocator_for_initializers->with_device_allocated_initializersFixes
c52bd2aFix MIGraphX registration.374a9d1Fix global environment thread poolsff08428Fix a segfault inTensor::clone.3d6c2a9Use new API to load the DirectML EP.5913ae0Make vcpkg builds work again.079ecb4Fix issues with multiple environment registration.❤️🧡💛💚💙💜
hasenbanck/resampler (resampler)
v0.5.1Compare Source
Fixed
ResamplerFirwith high resample ratios (#36)v0.5.0Compare Source
Added
ResamplerFir(#34)Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.