deps: bump the minor-and-patch group across 1 directory with 4 updates

[dependabot]

Bumps the minor-and-patch group with 4 updates in the / directory: oxideav-core, clap, rxing and ureq.

Updates oxideav-core from 0.1.34 to 0.1.36

Release notes

Sourced from oxideav-core's releases.

v0.1.36

Other

• document the register! dispatch contract + pin it with nested-module tests
• registration-ordered enumerations (names, ids, implementations, tags, schemes)
• "Resolution order" section in README + crate docs; CHANGELOG [Unreleased]
• extension-hint resolution priority + extension_candidates
• codec claim resolution priority + ranked tag / payload-magic candidates
• deterministic container-probe resolution + probe priority + probe_candidates

Fixed

• ContainerRegistry::probe_input resolved equal top scores in HashMap iteration order, so an input that two content probes scored identically opened as a different container from one process to the next. Probes are now kept in registration order and ranked by the documented resolution rule (score desc, priority asc, registration order asc). Default-priority registrations now resolve to the earlier-registered probe, deterministically.

Added

• A single documented resolution order for every multi-candidate lookup (README / crate docs "Resolution order"): evidence descending, then resolution priority ascending (lower is preferred, default DEFAULT_PRIORITY), then registration order. Extension hints keep their most-recent-wins contract at equal priority.
• Influence hooks (all additive; existing signatures unchanged): ContainerRegistry::register_probe_with_priority, ContainerRegistry::register_extension_with_priority, CodecInfo::with_resolution_priority (+ pub field CodecInfo::resolution_priority on the #[non_exhaustive] struct). The codec-claim priority is separate from CodecCapabilities::priority on purpose.
• Observation hooks returning the full ranked candidate list: ContainerRegistry::probe_candidates → Vec<ProbeCandidate>, ContainerRegistry::extension_candidates → Vec<ExtensionCandidate>, CodecRegistry::resolve_tag_candidates → Vec<TagCandidate>, CodecRegistry::resolve_payload_magic_candidates → Vec<PayloadMagicCandidate>; plus ContainerRegistry::probe_priority. The four candidate types are #[non_exhaustive] and re-exported at the crate root.
• Non-finite (NaN) codec probe confidences are discarded like non-positive ones instead of being ranked unpredictably.
• Every diagnostic enumeration is now registration-ordered instead of HashMap-ordered, so listings are identical across processes without a sort: ContainerRegistry::demuxer_names / muxer_names, CodecRegistry::all_implementations / decoder_ids / encoder_ids (order of each id's first implementation) / all_tag_registrations (registration order, then tag declaration

... (truncated)

Changelog

Sourced from oxideav-core's changelog.

0.1.36 - 2026-09-06

Other

• document the register! dispatch contract + pin it with nested-module tests
• registration-ordered enumerations (names, ids, implementations, tags, schemes)
• "Resolution order" section in README + crate docs; CHANGELOG [Unreleased]
• extension-hint resolution priority + extension_candidates
• codec claim resolution priority + ranked tag / payload-magic candidates
• deterministic container-probe resolution + probe priority + probe_candidates

Fixed

• ContainerRegistry::probe_input resolved equal top scores in HashMap iteration order, so an input that two content probes scored identically opened as a different container from one process to the next. Probes are now kept in registration order and ranked by the documented resolution rule (score desc, priority asc, registration order asc). Default-priority registrations now resolve to the earlier-registered probe, deterministically.

Added

• A single documented resolution order for every multi-candidate lookup (README / crate docs "Resolution order"): evidence descending, then resolution priority ascending (lower is preferred, default DEFAULT_PRIORITY), then registration order. Extension hints keep their most-recent-wins contract at equal priority.
• Influence hooks (all additive; existing signatures unchanged): ContainerRegistry::register_probe_with_priority, ContainerRegistry::register_extension_with_priority, CodecInfo::with_resolution_priority (+ pub field CodecInfo::resolution_priority on the #[non_exhaustive] struct). The codec-claim priority is separate from CodecCapabilities::priority on purpose.
• Observation hooks returning the full ranked candidate list: ContainerRegistry::probe_candidates → Vec<ProbeCandidate>, ContainerRegistry::extension_candidates → Vec<ExtensionCandidate>, CodecRegistry::resolve_tag_candidates → Vec<TagCandidate>, CodecRegistry::resolve_payload_magic_candidates → Vec<PayloadMagicCandidate>; plus ContainerRegistry::probe_priority. The four candidate types are #[non_exhaustive] and re-exported at the crate root.
• Non-finite (NaN) codec probe confidences are discarded like non-positive ones instead of being ranked unpredictably.
• Every diagnostic enumeration is now registration-ordered instead of HashMap-ordered, so listings are identical across processes without a sort: ContainerRegistry::demuxer_names / muxer_names, CodecRegistry::all_implementations / decoder_ids / encoder_ids (order of each id's first implementation) /

... (truncated)

Commits

• aa357dc chore: release v0.1.36 (#37)
• 7b8fe01 registry: document the register! dispatch contract + pin it with nested-modul...
• 174fdce registry: registration-ordered enumerations (names, ids, implementations, tag...
• 5299faf docs: "Resolution order" section in README + crate docs; CHANGELOG [Unreleased]
• 0abc803 registry: extension-hint resolution priority + extension_candidates
• 2eb228e registry: codec claim resolution priority + ranked tag / payload-magic candid...
• 69cc338 registry: deterministic container-probe resolution + probe priority + probe_c...
• 66bbd9a chore: release v0.1.35 (#36)
• defa866 format: 4:4:0 YUV ladder + scene-referred float family + plane-geometry helpers
• See full diff in compare view

Updates clap from 4.6.6 to 4.6.7

Release notes

Sourced from clap's releases.

v4.6.7

[4.6.7] - 2026-09-14

Features

• (derive) Add #[command(defer = <bool>)] attribute to opt-in to lazy initialisation of subcommands

Changelog

Sourced from clap's changelog.

[4.6.7] - 2026-09-14

Features

• (derive) Add #[command(defer = <bool>)] attribute to opt-in to lazy initialisation of subcommands

Commits

• d3e59a9 chore: Release
• d997f87 docs: Update changelog
• fb6058c Merge pull request #6409 from heaths/pwsh-support
• 2310870 test(complete): Add tests for completer_for_path
• 5967c17 refactor(complete): Move shell detection to Shells
• 594602b fix(complete): Detect pwsh for PowerShell
• 3a4f2d0 Merge pull request #6427 from clap-rs/renovate/shlex-2.x
• 67ebaed Merge pull request #6426 from clap-rs/renovate/actions-checkout-7.x
• c968b13 chore(deps): Update Rust crate shlex to v2
• 8f247cb chore(deps): Update actions/checkout action to v7
• Additional commits viewable in compare view

Updates rxing from 0.9.2 to 0.9.3

Release notes

Sourced from rxing's releases.

v0.9.3

What's Changed

• feat(cli): add option for the shape of a DataMatrix by @​mgkurtz in rxing-core/rxing#94
• fix(pdf417): bound bitstream parser control operands by the length descriptor by @​ginit64 in rxing-core/rxing#95
• Datamatrix GS1 fixes by @​JasperDeSutter in rxing-core/rxing#99
• fix: index underflow panic in TelepenReader::setCounters by @​jmortlock in rxing-core/rxing#96
• fix: fix an issue with ECI encoding markers above 170 (Binary == 899) by @​hschimke in rxing-core/rxing#98
• fix: use the encoded byte count for the PDF417 byte shift by @​tleish in rxing-core/rxing#101

New Contributors

• @​mgkurtz made their first contribution in rxing-core/rxing#94
• @​ginit64 made their first contribution in rxing-core/rxing#95
• @​jmortlock made their first contribution in rxing-core/rxing#96
• @​tleish made their first contribution in rxing-core/rxing#101

Full Changelog: rxing-core/rxing@v0.9.2...v0.9.3

Commits

• de4497b chore: version update for cli
• 268517d chore: cargo fmt
• ba19b4a chore: prepare for release
• 8b0e10e Merge pull request #101 from tleish/fix/pdf417-byte-shift-multibyte
• 71cb11c Merge pull request #98 from rxing-core/fixes/97-binary-eci
• b983d4e fix: use the encoded byte count for the PDF417 byte shift
• 2d86f01 test: add a failing case for a multi-byte character encoded with UTF-8
• 3654e29 fix: missed length calculation for eci 170
• 8f94f62 fix: expand fix for ISO646_Inv, ECI 170
• 7aafaaa fix: update ECI handling to support values up to 16383 and clarify encoding r...
• Additional commits viewable in compare view

Updates ureq from 3.4.0 to 3.4.2

Changelog

Sourced from ureq's changelog.

3.4.2

• Bump ureq-proto to 0.6.3 (fixes network-path references in redirects)
• Bypass pooling for request connection settings incompatible with the Agent #1201
• Try the next resolved address on unreachable/unavailable connect errors #1195

3.4.1

• Bump ureq-proto to 0.6.2 (fixes to parsing and headers) #1199
• Do not pool connections with unconsumed buffered input #1198
• Fix timeout budgets restarting and applying to later phases #1194
• Complete TLS handshake during connect so timeout_connect covers it #1193
• Speed up read_json for responses with a known, small body size #1191

Commits

• 2e9ef24 3.4.2
• b983841 Bump ureq-proto to 0.6.3
• 075a1d7 Respect request connection settings when pooling
• fb634de Try the next resolved address when a connect fails for that address only (#1195)
• cf4a3cd 3.4.1
• 9559d7b Bump ureq-proto to 0.6.2 (#1199)
• 9eb654c Do not pool a connection with unconsumed input (#1198)
• 5b81318 Anchor timeout budgets to phase boundaries (#1194)
• d480543 Complete TLS handshakes while connecting (#1193)
• 662410b Buffer read_json into memory when Content-Length is below the limit (#1191)
• See full diff 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

[dependabot]

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.