Skip to content

build(deps): bump the cargo-dependencies group across 1 directory with 5 updates - #31

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/cargo-dependencies-5191d6a30c
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/cargo-dependencies-5191d6a30c

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 11, 2026 •

Copy link
Copy Markdown
Contributor

Bumps the cargo-dependencies group with 5 updates in the / directory:

Package From To
moxcms 0.8.1 0.9.1
burn 0.21.0 0.22.0
burn-onnx 0.21.0 0.22.0
pyo3 0.29.2 0.29.3
tokio 1.53.1 1.53.2

Updates moxcms from 0.8.1 to 0.9.1

Release notes

Sourced from moxcms's releases.

0.9.1

What's Changed

Full Changelog: awxkee/moxcms@0.9.0...0.9.1

0.9.0

What's Changed

New Contributors

Full Changelog: awxkee/moxcms@0.8.1...0.9.0

Commits

Updates burn from 0.21.0 to 0.22.0

Release notes

Sourced from burn's releases.

v0.22.0

Summary

Burn 0.22.0 brings five months of improvements to training and inference, along with our biggest API update yet. Over the last four years, we've kept APIs stable where possible while collecting your feedback on what could be improved. This release brings Burn's API much closer to what we want for 1.0.

The biggest change is that models and tensors no longer carry a backend generic. Devices select where and how they run, and editing a model requires much less recompilation. The release also adds LoRA and QLoRA support, parameter groups and multiple optimizers, graph capture, and improvements to remote execution. New tensor operations, optimizers, and kernel improvements round out the release.

For more details, check out the release post on our website.

No More B: Backend

Burn is still built around the Backend trait, with composable support for autodiff, kernel fusion, and remote execution. User code now selects these capabilities through Device, while models are plain types:

use burn::{
    module::Module,
    nn::{Linear, LinearConfig},
    tensor::Device,
};
#[derive(Module, Debug)]
pub struct Model {
linear: Linear,
}
// Requires the cuda feature. Other options include Device::wgpu(..) and Device::flex().
let device = Device::cuda(0);
let model = Model {
linear: LinearConfig::new(4, 2).init(&device),
};

More of the infrastructure is now implemented in Rust: Pliron replaces the MLIR-based intermediate representation, and Turso replaces the bundled SQLite dependency. CubeCL also adds LLVM-based CUDA and AMD GPU compilation paths. These changes reduce reliance on bundled C and C++ components and make more of the stack accessible to Rust contributors, though LLVM remains a native dependency for the backends that use it. Clean builds can take longer even as model-edit rebuilds become much faster.

Changelog

Breaking changes and migration

See Migrating to Burn 0.22 in the Burn Book for the complete migration guide, including before-and-after examples for devices, autodiff, modules, training, datasets, tensor operations, and custom integrations.

Start by removing backend parameters such as Model<B> and Tensor<B, D>, selecting a Device, and enabling autodiff with device.autodiff() before initializing a training model and its inputs. Candle has been removed in this release, and NdArray and LibTorch are being deprecated.

Records now use burnpack. Legacy MessagePack, binary, and JSON recorder files must be loaded with an older compatible Burn version and exported through burn-store before importing the weights into 0.22. Follow the checkpoint migration instructions; this transfers model parameters, not legacy optimizer or scheduler state.

What's Changed

Tensor & Modules

... (truncated)

Commits
  • b8d75ad chore: update version to 0.22.0 (#5985)
  • f7364d3 feat(example): bf16 training for ag-news text classification (#5984)
  • e6bb5ab feat(quantization): a storage-tiled quantized tensor keeps its tiles (#5982)
  • 02c498f fix(remote): open streams only on connections a server dialed (#5980)
  • 12c9f4e docs: fix broken DeepWiki badge in README (#5966)
  • e8a6afb perf(cube): update cubecl for llvm TF32 support on CUDA (#5979)
  • 5b274df docs: 0.22 release documentation pass (#5973)
  • 90c6afe docs(book): update ONNX import chapter for burn-onnx 0.22 (#5972)
  • e36bdbf fix(derive): use field init shorthand in generated Config::new (#5981)
  • d9ca2e2 fix(quantization): round-trip a tensor packed along an outer axis (#5960)
  • Additional commits viewable in compare view

Updates burn-onnx from 0.21.0 to 0.22.0

Release notes

Sourced from burn-onnx's releases.

burn-onnx v0.22.0

burn-onnx 0.22.0 ships alongside Burn 0.22.0. This cycle brought ONNX export (experimental), custom op hooks for models with operators we don't implement, Burn's new backend-generic-free API in all generated code, and a lot of conformance work. The upstream ONNX test suite now has 1,190 passing tests, up from 717 in 0.21.

Headline numbers

  • 1,190 / 1,765 upstream ONNX backend node tests passing, up from 717 / 1,615 in 0.21.0. The vendored suite moved from ONNX v1.19.0 to v1.22.0 (#555).
  • skip-codegen dropped from 504 to 451, skip-compile from 215 to 78, fail-compare from 179 to 40.
  • 173 operators supported for import (up from 167), and opset compliance tests now cover every registered op (#573).
  • Malformed models no longer panic: 0 panics across 69,500 byte-level mutations of the test corpus (#584).

Burn 0.22: no more backend generic

Burn 0.22 dropped the B: Backend type parameter (tracel-ai/burn#4934). Generated models follow suit: Model<B> is now Model, Tensor<B, R> is Tensor<R>, and the device is a single runtime-dispatched Device (#403).

// 0.21
let model: Model<Backend> = Model::from_file("model.bpk", &device);
// 0.22
let model = Model::from_file("model.bpk", &device);

Regenerate your models with 0.22 and drop the backend generic from the code that calls them.

ONNX export (experimental)

Behind the new export feature, OnnxExporter captures a Burn module's forward pass and writes it out as an ONNX model (#454). export_dynamic marks axes like the batch size as symbolic. ResNet-18 round-trips and passes the ONNX checker. Coverage is growing: Conv1d, slicing, indexing, tensor creation, reductions and Pad all lower directly (#484, #498, #502). Anything that can't be lowered yet comes back as ExportError::UnsupportedOperation, not a broken model.

burn-onnx = { version = "0.22", features = ["export"] }
use burn_onnx::export::OnnxExporter;
let onnx = OnnxExporter::new().export(&model, sample, MyModel::forward)?;

Custom op hooks

An unsupported operator no longer blocks the whole import (#445, closes #23). Two extension points are registered on ModelGen:

  • CustomOp handles an op by (op_type, domain), such as a com.microsoft vendor op or an op burn-onnx doesn't implement yet. You provide type inference and codegen.
  • OpOverride replaces the generated code for a built-in op, for example to route every MatMul to your own kernel.
ModelGen::new()
    .input("model.onnx")
    .out_dir("model/")
    .register_custom_op(ScaleBias)
</tr></table> 

... (truncated)

Commits
  • ac7da7f Split: accept Shape as split sizes input (#592)
  • 1c6cdef Improve documentation for the 0.22 release (#590)
  • 04f4755 Bump burn rev to latest main (#588)
  • 7d45944 Bump burn rev to latest main (#586)
  • 4f90044 Harden ONNX parsing against malformed models before release (#584)
  • 8525b05 Bump burn rev to 3bf6e039 and adapt to API changes (#583)
  • 1b1ba73 Bump burn rev to latest main (#579)
  • 37383e0 Rewrite SplitToSequence -> SequenceAt into Gather/Slice (#578)
  • 02a85d6 Compute MaxPool and LpPool output static shapes from the pool attributes (#577)
  • c147352 Type untyped Loop body inputs from their v_initial (#576)
  • Additional commits viewable in compare view

Updates pyo3 from 0.29.2 to 0.29.3

Release notes

Sourced from pyo3's releases.

PyO3 0.29.3

This release is a series of fixes worth landing to the PyO3 0.29 series; the PyO3 0.30 release is planned to follow within a few weeks, however during the development cycle a number of rough edges were discovered which were deemed worth a backport.

The patch broadly includes:

  • a further fix the to the opt-out of raw-dylib linking for Windows introduced in PyO3 0.29.1 (the switch to raw-dylib linking was introduced in PyO3 0.29.0),
  • fixes to support GraalPy on windows,
  • a handful of small performance optimizations,
  • a number of non-breaking fixes to the experimental-inspect type stub generation (expect more improvements in 0.30), and
  • various other bugfixes such as to FFI definitions, to resolve crashes, and to fix clippy lints caused by PyO3 macros.

For a full list of the exact fixes please consult the CHANGELOG.

Thank you to the following contributors for the improvements:

@​adamgerhant-ai @​alex @​bschoenmaeckers @​charliermarsh @​chirizxc @​davidhewitt @​dependabot[bot] @​dylanpulver @​exg @​FranciscoTGouveia @​JMak-Security @​jonasdedden @​jorenham @​konstin @​latent-9 @​mejrs @​ngoldbaum @​Person-93 @​PeterFaiman @​sneakers-the-rat

Changelog

Sourced from pyo3's changelog.

[0.29.3] - 2026-09-30

Packaging

  • Support GraalPy on Windows. #6406

Added

  • Add FFI definitions PyModule_GetState_DuringGC, PyModule_GetToken_DuringGC, PyObject_GetTypeData_DuringGC, PyType_GetModuleState_DuringGC, PyType_GetBaseByToken_DuringGC, PyType_GetModule_DuringGC, and PyType_GetModuleByToken_DuringGC for Python 3.15 and up. #6419

Changed

  • Optimize u128/i128 conversions on Python 3.15+. #6160
  • Preallocate output sets when extracting Python set and frozenset values into Rust hash sets. #6225
  • Optimize PyBytes::as_bytes() when not using abi3 or abi3t. #6377

Removed

  • Remove FFI definitions PyExc_RecursionErrorInst and Py_UseClassExceptionsFlag (not present in supported Python versions). #6421

Fixed

  • Revert removal of FFI definition _PyFrameEvalFunction, _PyInterpreterState_GetEvalFrameFunc and _PyInterpreterState_SetEvalFrameFunc, which are not currently treated as CPython private API despite their name. #6195
  • Fix FFI definition PyUnstable_Eval_RequestCodeExtraIndex FFI binding to link to the private CPython symbol on Python versions before 3.12. #6195
  • Fix FFI definitions PyByteArray_GET_SIZE, PyList_GET_SIZE, and PySet_GET_SIZE to use an atomic load for free-threaded Python. #6230
  • experimental-inspect: deduplicate repeated members of a type union in the generated stubs, and put a space on both sides of the | rather than only before it. #6273
  • experimental-inspect: __next__ and __anext__ returning Option<T> (or PyResult<Option<T>>) are now introspected as returning T, since None stops the iteration instead of being yielded. #6274
  • Fix clippy::clone_on_copy warnings triggered on nightly Rust by #[pyclass(from_py_object)] on classes which implement Copy. #6309
  • experimental-inspect: __pow__, __rpow__ and __get__ now introspect their trailing argument as defaulting to None, matching the CPython slot wrappers which substitute None when it is omitted. #6363
  • experimental-inspect: fix the stubs of a package nested inside another package being written into a directory named after its parent instead of its own name. #6365
  • Fix many unresolved symbols when linking for PyPy due to incorrect link names in pyo3-ffi. #6389
  • Fix empty tuple type hints being rendered as invalid tuple[] instead of tuple[()] in generated stubs and PyStaticExpr display. #6393
  • experimental-inspect: escape stub docstrings to prevent invalid Python syntax. #6394
  • experimental-inspect: fix the generated type annotation for PyBuffer on python <3.12 by using typing_extensions.Buffer instead of collections.abc.Buffer. #6395
  • Fix string constants containing control characters rendering as invalid Python in Display for PyStaticExpr. #6397
  • Fix crash when a detached thread is terminated while trying to reattach during interpreter finalization. #6404
  • Fix link failures on 32-bit Windows when raw-dylib linking is disabled. #6410
  • Fix DLL load failures on Windows with PyPy when raw-dylib linking is disabled. #6410
  • Fix FFI definition PyVectorcall_Call failing to link on Python 3.11 and older. #6410
  • Fix many unresolved data symbols when linking for PyPy due to incorrect link names in pyo3-ffi. #6421
  • Fix linker errors on PyPy for outdated FFI definitions where PyPy moved from a function to a macro. #6422
  • Fix crash when GC traverses a #[pyclass] type object during class attribute initialization. #6453
Commits

Updates tokio from 1.53.1 to 1.53.2

Release notes

Sourced from tokio's releases.

Tokio v1.53.2

1.53.2 (October 3rd, 2026)

Fixed

  • fs: handle integer overflow in buffered relative seek (#8574)
  • io: revert "always cleanup AsyncFd registration list on deregister" (#8540)
  • process: unregister Windows wait before closing child handle (#8564)
  • rt: drop blocking pool mutex before shutting down rejected task (#8562)
  • sync: fix mpsc index wraparound in block reclamation (#8546)
  • sync: forget mpsc Permit before sending value (#8560)
  • sync: validate MAX_PERMITS in Semaphore::acquire (#8548)
  • sync: wake broadcast Sender::closed outside mutex (#8558)
  • task: drop replaced waker outside lock in JoinSet (#8554)
  • time: drop timer lock before dropping waker in clear_entry (#8552)
  • time: expire timers directly on shutdown without rotating wheel (#8570)

Fixed (unstable)

  • fs: clamp io_uring read length to u32::MAX (#8572)
  • rt: ignore current_thread task dumps from other runtimes (#8544)
  • rt: preserve io_uring context if a completion waker panics (#8566)
  • sync: fix semaphore use-after-free and permit leak on tracing panic (#8542)
  • taskdump: restore deferred leaf wakes during capture (#8445)
  • time: drop stored waker when cancelling alt timer entry (#8550)

#8445: tokio-rs/tokio#8445 #8572: tokio-rs/tokio#8572 #8540: tokio-rs/tokio#8540 #8542: tokio-rs/tokio#8542 #8544: tokio-rs/tokio#8544 #8546: tokio-rs/tokio#8546 #8548: tokio-rs/tokio#8548 #8550: tokio-rs/tokio#8550 #8552: tokio-rs/tokio#8552 #8554: tokio-rs/tokio#8554 #8558: tokio-rs/tokio#8558 #8560: tokio-rs/tokio#8560 #8562: tokio-rs/tokio#8562 #8564: tokio-rs/tokio#8564 #8566: tokio-rs/tokio#8566 #8570: tokio-rs/tokio#8570 #8574: tokio-rs/tokio#8574

Commits
  • ff0c406 chore: prepare Tokio v1.53.2 (#8580)
  • a762700 Merge 'tokio-1.51.5' into 'tokio-1.53.x' (#8577)
  • ec31a9f chore: prepare Tokio v1.51.5 (#8579)
  • 625c851 sync: assign semaphore permits before emitting tracing event (#8542)
  • 832dd23 sync: avoid leaking semaphore permits on tracing panic (#8542)
  • 826954a sync: unlink semaphore waiter before emitting tracing event (#8542)
  • 9a47992 process: unregister Windows wait before closing child handle (#8564)
  • 2fc5972 fs: handle integer overflow in buffered relative seek (#8574)
  • 85a6d13 io: revert "always cleanup AsyncFd registration list on deregister" (#8540)
  • 436faa2 rt: drop blocking pool mutex before shutting down rejected task (#8562)
  • Additional 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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

…h 5 updates

Bumps the cargo-dependencies group with 5 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [moxcms](https://github.com/awxkee/moxcms) | `0.8.1` | `0.9.1` |
| [burn](https://github.com/tracel-ai/burn) | `0.21.0` | `0.22.0` |
| [burn-onnx](https://github.com/tracel-ai/burn-onnx) | `0.21.0` | `0.22.0` |
| [pyo3](https://github.com/pyo3/pyo3) | `0.29.2` | `0.29.3` |
| [tokio](https://github.com/tokio-rs/tokio) | `1.53.1` | `1.53.2` |



Updates `moxcms` from 0.8.1 to 0.9.1
- [Release notes](https://github.com/awxkee/moxcms/releases)
- [Commits](awxkee/moxcms@0.8.1...0.9.1)

Updates `burn` from 0.21.0 to 0.22.0
- [Release notes](https://github.com/tracel-ai/burn/releases)
- [Commits](tracel-ai/burn@v0.21.0...v0.22.0)

Updates `burn-onnx` from 0.21.0 to 0.22.0
- [Release notes](https://github.com/tracel-ai/burn-onnx/releases)
- [Commits](tracel-ai/burn-onnx@v0.21.0...v0.22.0)

Updates `pyo3` from 0.29.2 to 0.29.3
- [Release notes](https://github.com/pyo3/pyo3/releases)
- [Changelog](https://github.com/PyO3/pyo3/blob/main/CHANGELOG.md)
- [Commits](PyO3/pyo3@v0.29.2...v0.29.3)

Updates `tokio` from 1.53.1 to 1.53.2
- [Release notes](https://github.com/tokio-rs/tokio/releases)
- [Commits](tokio-rs/tokio@tokio-1.53.1...tokio-1.53.2)

---
updated-dependencies:
- dependency-name: moxcms
  dependency-version: 0.9.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: cargo-dependencies
- dependency-name: burn
  dependency-version: 0.22.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: cargo-dependencies
- dependency-name: burn-onnx
  dependency-version: 0.22.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: cargo-dependencies
- dependency-name: pyo3
  dependency-version: 0.29.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: cargo-dependencies
- dependency-name: tokio
  dependency-version: 1.53.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: cargo-dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file rust Pull requests that update rust code labels Oct 11, 2026
Stefatorus pushed a commit that referenced this pull request Oct 11, 2026
…0.22), minus a toolchain pin

Dependabot's two open PRs (#31 cargo, #21 Actions) were red, for reasons of their own:

- #31, cargo: moxcms 0.9 needs rustc 1.89, the MSRV job's 1.88 failed; THIRD_PARTY.md was
  not regenerated; its quality-ratchet failure was the base's (fixed in #33). Now: moxcms 0.9,
  the workspace rust-version and the MSRV job at 1.89 (CONTRIBUTING and AI_USAGE state it),
  THIRD_PARTY.md regenerated, tokio 1.53.2 and pyo3 0.29.3 in both lockfiles that carry them
  (studio's own lock follows moxcms). Output is byte-identical to the 0.3.0 release binary on
  237 sampled traces.
- burn 0.22 (and burn-onnx and burn-store, which the PR left at 0.21): not a drop-in. The
  backend is no longer a type parameter but part of the `Device` the weights load onto, the
  generated `Model` is no longer generic, `burnpack` is no longer a burn-store feature and
  `into_vec` is `try_into_vec`. `Restorer` is now one type holding a device; the backend
  features pick it (`cuda(0)`, `wgpu`, `flex`). The Burn path did not build on main before
  this either: build.rs formatted a `PathBuf` with `{}` and passed it to `input(&str)`.
  Checked on the flex (CPU) backend: `--restore on` through the Burn weights gives the same
  SVG as through ONNX Runtime on three web-tier JPEGs. CUDA and wgpu are untested here.
- #21, Actions: the bump included `dtolnay/rust-toolchain@1.98.0` -> `@1.120.0`; that tag is
  the Rust toolchain the job installs, not an action version, and 1.120.0 does not exist, so
  every job failed at "Set up toolchain". That one stays; the rest of the bump (checkout 7,
  upload-artifact 7, download-artifact 8, setup-python 7, setup-node 7, setup-go 7,
  setup-java 6, setup-dotnet 6, docker/* 4-7, gh-release 3, pages 5) is applied, and
  dependabot.yml now ignores the toolchain action so it is not proposed again.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016AZWMqqHhRQ337N5EWhNC6
@dependabot @github

dependabot Bot commented on behalf of github Oct 11, 2026

Copy link
Copy Markdown
Contributor Author

Looks like these dependencies are updatable in another way, so this is no longer needed.

@dependabot dependabot Bot closed this Oct 11, 2026
@dependabot
dependabot Bot deleted the dependabot/cargo/cargo-dependencies-5191d6a30c branch October 11, 2026 16:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file rust Pull requests that update rust code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants