Skip to content

chore(deps): update cargo minor/patch updates - #1792

Merged
mergify[bot] merged 1 commit into
mainfrom
renovate/cargo-minorpatch-updates
Sep 18, 2026
Merged

mergify[bot] merged 1 commit into
mainfrom
renovate/cargo-minorpatch-updates

Conversation

@renovate

@renovate renovate Bot commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
console workspace.dependencies patch 0.16.40.16.6
jsonschema workspace.dependencies minor 0.550.56
reqwest workspace.dependencies patch 0.13.40.13.5

Release Notes

console-rs/console (console)

v0.16.6

Compare Source

What's Changed

Stranger6667/jsonschema (jsonschema)

v0.56.0

Added
  • canonical::RawReason, what stopped a run from modeling a document, and canonical::RawView, carrying it beside the document and a pointer to the subschema the run stopped on.
  • ValidationOptions::is_known_format, whether a format of that name is checked under a draft.
Changed
  • BREAKING: canonical::CanonicalView::Raw carries a canonical::RawView in place of the document alone.
  • Canonicalization of a oneOf whose branches share a region too wide to expand, which spent the document's whole intersection allowance on that choice and kept the document Raw.
Performance
  • Preparing or building a schema that names no base URI parses the default one once for the process instead of once per schema.
  • Canonicalizing several subschemas of one prepared document compiles each pattern once for the document instead of once per call.
  • Canonicalization reads the facets no checker covers once per node instead of once per containment query.
seanmonstar/reqwest (reqwest)

v0.13.5

Compare Source

  • Add Error::is_dns() to identify errors caused by DNS resolution failures.
  • Add ClientBuilder::http1_max_headers(usize) to configure the maximum number of headers accepted in an HTTP/1 response (default 100).
  • Add TLS version to TlsInfo extension.
  • Fix hickory-dns feature to use Ipv6AndIpv4 strategy to prefer IPv6.
  • Fix sending wrong proxy-auth if multiple proxies intercept a given URL.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "before 5am on monday"
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@mergify
mergify Bot had a problem deploying to Mergify Merge Protections August 31, 2026 01:57 Failure
@renovate
renovate Bot had a problem deploying to func-tests-live August 31, 2026 01:57 Failure
@mergify

mergify Bot commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

Merge Protections

🟢 All 6 merge protections satisfied — ready to merge.

Show 6 satisfied protections

🟢 🤖 Continuous Integration

  • all of:
    • check-success=ci-gate

🟢 👀 Review Requirements

  • any of:
    • author = renovate[bot]
    • #approved-reviews-by>=2
    • author = dependabot[bot]
    • author = mergify-ci-bot

🟢 Enforce conventional commit

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

  • title ~= ^(fix|feat|internal|docs|style|refactor|perf|test|build|ci|chore|revert|ui)(?:\(.+\))?!?:

🟢 🔎 Reviews

  • #changes-requested-reviews-by = 0
  • #review-requested = 0
  • #review-threads-unresolved = 0

🟢 📕 PR description

  • body ~= (?ms:.{48,})

🟢 🚦 Auto-queue

When all merge protections are satisfied, this pull request will be queued automatically.

@renovate
renovate Bot force-pushed the renovate/cargo-minorpatch-updates branch from 1b1cc8d to 86cc5da Compare September 2, 2026 22:33
@mergify
mergify Bot had a problem deploying to Mergify Merge Protections September 2, 2026 22:33 Failure
@renovate
renovate Bot force-pushed the renovate/cargo-minorpatch-updates branch from 86cc5da to b1dfa99 Compare September 4, 2026 06:04
@mergify
mergify Bot had a problem deploying to Mergify Merge Protections September 4, 2026 06:04 Failure
@renovate
renovate Bot force-pushed the renovate/cargo-minorpatch-updates branch from b1dfa99 to d397fcb Compare September 7, 2026 22:39
@mergify
mergify Bot had a problem deploying to Mergify Merge Protections September 7, 2026 22:39 Failure
@renovate
renovate Bot force-pushed the renovate/cargo-minorpatch-updates branch from d397fcb to 5939bfa Compare September 9, 2026 08:21
@mergify
mergify Bot had a problem deploying to Mergify Merge Protections September 9, 2026 08:25 Failure
@renovate
renovate Bot force-pushed the renovate/cargo-minorpatch-updates branch from 5939bfa to 7d3ecec Compare September 10, 2026 02:02
@mergify
mergify Bot had a problem deploying to Mergify Merge Protections September 10, 2026 02:03 Failure
@renovate
renovate Bot force-pushed the renovate/cargo-minorpatch-updates branch from 7d3ecec to a4c74c7 Compare September 13, 2026 01:24
@mergify
mergify Bot had a problem deploying to Mergify Merge Protections September 13, 2026 01:24 Failure
@renovate
renovate Bot force-pushed the renovate/cargo-minorpatch-updates branch from a4c74c7 to a0c6e65 Compare September 13, 2026 21:10
@mergify
mergify Bot had a problem deploying to Mergify Merge Protections September 13, 2026 21:11 Failure
@renovate
renovate Bot force-pushed the renovate/cargo-minorpatch-updates branch from a0c6e65 to c149359 Compare September 15, 2026 11:54
@mergify
mergify Bot had a problem deploying to Mergify Merge Protections September 15, 2026 11:54 Failure
@renovate
renovate Bot force-pushed the renovate/cargo-minorpatch-updates branch from c149359 to a12a0ab Compare September 15, 2026 15:40
@mergify
mergify Bot had a problem deploying to Mergify Merge Protections September 15, 2026 15:46 Failure
@renovate
renovate Bot force-pushed the renovate/cargo-minorpatch-updates branch from a12a0ab to 4f9e1b7 Compare September 15, 2026 23:58
@mergify
mergify Bot had a problem deploying to Mergify Merge Protections September 15, 2026 23:58 Failure
@renovate
renovate Bot force-pushed the renovate/cargo-minorpatch-updates branch from 4f9e1b7 to 8391beb Compare September 16, 2026 13:52
@mergify
mergify Bot had a problem deploying to Mergify Merge Protections September 16, 2026 13:52 Failure
jd added a commit that referenced this pull request Sep 16, 2026
flate2 1.1.9 -> 1.1.10, quick-xml 0.41 -> 0.42, jsonschema 0.49 -> 0.55.
Supersedes renovate's #1792, which never got past `renovate/artifacts`:
the bot regenerates Cargo.lock itself and couldn't, so every downstream
job (rust, MSRV, cargo-deny, wheels, smoke tests, ci-gate) was red for
want of a lockfile, not a real break in the bump.

quick-xml 0.42 replaces its whole byte-oriented name/text API with
`&str` (`QName` is now `QName<'a>(pub &'a str)`, and `BytesText` /
`BytesCData` / `BytesRef` all implement `AsRef<str>` instead of
`AsRef<[u8]>`), since the crate only ever accepted UTF-8 XML anyway.
Update the JUnit parser's `local_name()` and every attribute/tag match
in junit.rs from byte-string patterns to string patterns to match.

jsonschema 0.49 -> 0.55 is six minor versions of a pre-1.0 crate; read
the crate's changelog end to end rather than trusting a clean compile.
The one behavior-relevant note (0.52.0: with `default-features = false`,
`idn-hostname`/`idn-email` need the new `idna` feature or they're
unknown formats) doesn't apply here — the Mergify config schema's own
`format` keywords (`date-time`, `duration`, `regex`, `simple-template`,
`template`) are all custom or already outside that set, so they were
unknown formats (silently accepted) before this bump too. No code
changes needed for `mergify-config`'s `validate_against_schema`, which
only uses `options().build()` / `iter_errors()` / `instance_path()` —
none of which changed shape across the six releases.

Cargo.lock's other moves (jsonschema-regex, jsonschema-value,
referencing pinned in lockstep with jsonschema; fraction and
num-bigint pulled in by jsonschema's own updated deps; miniz_oxide and
an inactive optional zlib-rs pulled in by flate2) are all forced by
these three bumps, not separate dependency moves.

Verified locally against the exact CI steps: `cargo fmt --all --check`,
`cargo clippy --workspace --all-targets --all-features --locked --
-D warnings`, `cargo test --workspace --all-features --locked` (668
passed), `cargo build --workspace --all-features --locked`, all green.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Change-Id: I34925c0376293e993db7b1048faa55005f3d1b9e
@renovate
renovate Bot force-pushed the renovate/cargo-minorpatch-updates branch from 8391beb to ebc58f9 Compare September 17, 2026 17:40
@mergify
mergify Bot had a problem deploying to Mergify Merge Protections September 17, 2026 17:40 Failure
mergify Bot pushed a commit that referenced this pull request Sep 18, 2026
flate2 1.1.9 -> 1.1.10, quick-xml 0.41 -> 0.42, jsonschema 0.49 -> 0.55.
Supersedes renovate's #1792, which never got past `renovate/artifacts`:
the bot regenerates Cargo.lock itself and couldn't, so every downstream
job (rust, MSRV, cargo-deny, wheels, smoke tests, ci-gate) was red for
want of a lockfile, not a real break in the bump.

quick-xml 0.42 replaces its whole byte-oriented name/text API with
`&str` (`QName` is now `QName<'a>(pub &'a str)`, and `BytesText` /
`BytesCData` / `BytesRef` all implement `AsRef<str>` instead of
`AsRef<[u8]>`), since the crate only ever accepted UTF-8 XML anyway.
Update the JUnit parser's `local_name()` and every attribute/tag match
in junit.rs from byte-string patterns to string patterns to match.

jsonschema 0.49 -> 0.55 is six minor versions of a pre-1.0 crate; read
the crate's changelog end to end rather than trusting a clean compile.
The one behavior-relevant note (0.52.0: with `default-features = false`,
`idn-hostname`/`idn-email` need the new `idna` feature or they're
unknown formats) doesn't apply here — the Mergify config schema's own
`format` keywords (`date-time`, `duration`, `regex`, `simple-template`,
`template`) are all custom or already outside that set, so they were
unknown formats (silently accepted) before this bump too. No code
changes needed for `mergify-config`'s `validate_against_schema`, which
only uses `options().build()` / `iter_errors()` / `instance_path()` —
none of which changed shape across the six releases.

Cargo.lock's other moves (jsonschema-regex, jsonschema-value,
referencing pinned in lockstep with jsonschema; fraction and
num-bigint pulled in by jsonschema's own updated deps; miniz_oxide and
an inactive optional zlib-rs pulled in by flate2) are all forced by
these three bumps, not separate dependency moves.

Verified locally against the exact CI steps: `cargo fmt --all --check`,
`cargo clippy --workspace --all-targets --all-features --locked --
-D warnings`, `cargo test --workspace --all-features --locked` (668
passed), `cargo build --workspace --all-features --locked`, all green.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@renovate
renovate Bot force-pushed the renovate/cargo-minorpatch-updates branch from ebc58f9 to f72f557 Compare September 18, 2026 09:13
@renovate
renovate Bot deployed to func-tests-live September 18, 2026 09:13 Active
@mergify
mergify Bot deployed to Mergify Merge Protections September 18, 2026 09:17 Active
@mergify

mergify Bot commented Sep 18, 2026

Copy link
Copy Markdown
Contributor

Merge Queue Status

  • Entered queue2026-09-18 09:24 UTC · Rule: dependencies · triggered by merge protections
  • Checks skipped · PR is already up-to-date
  • Merged2026-09-18 09:31 UTC · at f72f557db8d97fa633f2e12dd516f554e08502e0 · fast-forward

This pull request spent 6 minutes 59 seconds in the queue, including 3 seconds running CI.

Required conditions to merge

@mergify mergify Bot added the queued label Sep 18, 2026
@mergify
mergify Bot merged commit f72f557 into main Sep 18, 2026
23 checks passed
@mergify
mergify Bot deleted the renovate/cargo-minorpatch-updates branch September 18, 2026 09:31
@mergify mergify Bot removed the queued label Sep 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

0 participants