cargo: bump the cargo-dependencies group with 5 updates

[dependabot]

Bumps the cargo-dependencies group with 5 updates:

Package	From	To
either	1.17.0	1.18.0
gix-ignore	0.22.0	0.22.1
jsonschema	0.49.9	0.51.0
ref-cast	1.0.26	1.0.27
syn	3.0.3	3.0.4

Updates either from 1.17.0 to 1.18.0

Changelog

Sourced from either's changelog.

• 1.18.0 - 2026-08-20
  • Add trait impls akin to Itertools::partition_map, by @​cuviper (#144)
    • Extend<Either<L, R>> for (A, B)
    • FromIterator<Either<L, R>> for (A, B)

Commits

• ce6f07f Merge pull request #144 from cuviper/partition_map
• 30f29a9 Release 1.18.0
• 500b0fb Add trait impls akin to partition_map
• 1b7187b Fix the RELEASES link
• 0f1b60b Merge pull request #142 from cuviper/readme
• 4a7f162 Update badges
• 0adab0a Backfill pubtime dates in RELEASES.md
• e9e5497 Move changes to RELEASES.md
• a1f4a7e Consolidate to one README
• 5928a2b Convert README.rst to README.md
• See full diff in compare view

Updates gix-ignore from 0.22.0 to 0.22.1

Release notes

Sourced from gix-ignore's releases.

gix-ignore v0.22.1

Bug Fixes

• parse !$ ignore lines as negations unless precious files are enabled Git has no notion of precious files, so !$foo is an ordinary negation of a file literally named $foo. gitoxide dropped such lines outright, even with support_precious off - the mode Lines::new documents as backward-compatible.

  Precious support landed in 890efd591 with $ handled unconditionally, which made rejecting !$ correct at the time. 828e9035a made the parser stateful and gated the $ branch on support_precious, but the !$ check in the else branch kept its unconditional form. This applies the same gate to it.

  Precious mode is unchanged: !$ is still rejected there.

Commit Statistics

• 6 commits contributed to the release over the course of 30 calendar days.
• 30 days passed between releases.
• 1 commit was understood as conventional.
• 0 issues like '(#ID)' were seen in commit messages

Commit Details

• Uncategorized
  • Update manifests prior to release (ebe9095)
  • Merge pull request #2885 from ameyypawar/ignore-negated-dollar (23388e1)
  • Parse !$ ignore lines as negations unless precious files are enabled (d4b2050)
  • Merge pull request #2867 from GitoxideLabs/fix-url-authority-parsing (cc3ee80)
  • Release gix-path v0.12.4, gix-command v0.9.2, gix-config-value v0.19.1, gix-url v0.37.1, gix-credentials v0.39.1, gix-transport v0.58.1 (ab4fcb0)
  • Merge pull request #2812 from GitoxideLabs/report-july (ae8845a)

Changelog

Sourced from gix-ignore's changelog.

0.22.1 (2023-02-17)

Bug Fixes

• re-enable local-time support for all binaries The time improved the way one can opt-in to potential unsoundness in their local time support, forcing the application to make that decision at runtime.

Commit Statistics

• 1 commit contributed to the release.
• 1 commit was understood as conventional.
• 0 issues like '(#ID)' were seen in commit messages

Commit Details

• Uncategorized
  • Re-enable local-time support for all binaries (73372d0)

Commits

• d2af4ed Release gix-error v0.3.0, gix-date v0.16.0, gix-actor v0.42.0, gix-validate v...
• ebe9095 update manifests prior to release
• 68c263b report proofing
• 0d8bd1d Report August 2026
• 7424676 Merge pull request #2930 from GitoxideLabs/gix-notes
• 5c8d935 thanks clippy
• d934f5b feat: expose git notes in gix::Repository
• dc556e4 feat(gix-glob): add Pattern::has_wildcard()
• d21b52a feat: support note mutation in gix-note
• 7f7367c feat(gix-hash): add allocation-free prefix hex utilities
• Additional commits viewable in compare view

Updates jsonschema from 0.49.9 to 0.51.0

Release notes

Sourced from jsonschema's releases.

[CLI] Release 0.51.0

No release notes provided.

[Python] Release 0.51.0

Added

• vocabularies option, declaring support for a vocabulary this library does not implement.

Fixed

• The uniqueItems length ceiling not reading an items or contains schema written as a $ref.
• The Draft 2020-12 Format-Assertion vocabulary read as an annotation, so a meta-schema requiring it accepted values its format rejects.
• An unrecognized format accepted under a meta-schema requiring the Format-Assertion vocabulary (it should be rejected).
• A meta-schema requiring a vocabulary this library does not implement accepted (it should be rejected).
• The Draft 2019-09 Format vocabulary declared true read as an annotation, so a meta-schema requiring it accepted values its format rejects.
• The bundled https://json-schema.org/draft/2020-12/meta/format-assertion meta-schema not declaring its vocabulary, so a schema written against it annotated format instead of asserting it.
• A meta-schema without $id keeping its $vocabulary unread, so a schema written against it got every Draft 2020-12 vocabulary.
• A schema naming a bundled vocabulary meta-schema as its $schema rejected as an unknown meta-schema (it should build).
• The regex format reading the Rust regex dialect (it should read the ECMA-262 dialect in Unicode mode).
• The uri-template format rejecting an apostrophe in a literal (it should accept it, per RFC 6570 errata 6937).
• The duration format accepting weeks combined with a time part, such as P1WT1H (it should reject it).
• Stack overflow compiling unevaluatedProperties or unevaluatedItems beside a $ref that cycles back to the node, written as #, through its $id, or through a chain of definitions.

Performance

• Building unevaluatedProperties or unevaluatedItems over a deep allOf or $ref chain costs its depth instead of its square.

[Ruby] Release 0.51.0

Added

• vocabularies option, declaring support for a vocabulary this library does not implement.

Fixed

• The uniqueItems length ceiling not reading an items or contains schema written as a $ref.
• The Draft 2020-12 Format-Assertion vocabulary read as an annotation, so a meta-schema requiring it accepted values its format rejects.
• An unrecognized format accepted under a meta-schema requiring the Format-Assertion vocabulary (it should be rejected).
• A meta-schema requiring a vocabulary this library does not implement accepted (it should be rejected).
• The Draft 2019-09 Format vocabulary declared true read as an annotation, so a meta-schema requiring it accepted values its format rejects.
• The bundled https://json-schema.org/draft/2020-12/meta/format-assertion meta-schema not declaring its vocabulary, so a schema written against it annotated format instead of asserting it.
• A meta-schema without $id keeping its $vocabulary unread, so a schema written against it got every Draft 2020-12 vocabulary.
• A schema naming a bundled vocabulary meta-schema as its $schema rejected as an unknown meta-schema (it should build).
• The regex format reading the Rust regex dialect (it should read the ECMA-262 dialect in Unicode mode).
• The uri-template format rejecting an apostrophe in a literal (it should accept it, per RFC 6570 errata 6937).
• The duration format accepting weeks combined with a time part, such as P1WT1H (it should reject it).
• Stack overflow compiling unevaluatedProperties or unevaluatedItems beside a $ref that cycles back to the node, written as #, through its $id, or through a chain of definitions.

Performance

• Building unevaluatedProperties or unevaluatedItems over a deep allOf or $ref chain costs its depth instead of its square.

... (truncated)

Changelog

Sourced from jsonschema's changelog.

[0.51.0] - 2026-08-23

Added

• ValidationOptions::with_vocabulary and the vocabularies attribute on jsonschema::validator, declaring support for a vocabulary this crate does not implement.
• The --vocabulary flag of jsonschema validate.

Changed

• Vocabulary gained the FormatAssertion variant, which its Draft 2020-12 URI parses to instead of Vocabulary::Custom, and is marked non_exhaustive.

Fixed

• The uniqueItems length ceiling not reading an items or contains schema written as a $ref.
• The Draft 2020-12 Format-Assertion vocabulary read as an annotation, so a meta-schema requiring it accepted values its format rejects.
• An unrecognized format accepted under a meta-schema requiring the Format-Assertion vocabulary (it should be rejected).
• A meta-schema requiring a vocabulary this crate does not implement accepted (it should be rejected).
• The Draft 2019-09 Format vocabulary declared true read as an annotation, so a meta-schema requiring it accepted values its format rejects.
• The bundled https://json-schema.org/draft/2020-12/meta/format-assertion meta-schema not declaring its vocabulary, so a schema written against it annotated format instead of asserting it.
• A meta-schema without $id keeping its $vocabulary unread, so a schema written against it got every Draft 2020-12 vocabulary.
• A schema naming a bundled vocabulary meta-schema as its $schema rejected as an unknown meta-schema (it should build).
• The regex format reading the Rust regex dialect (it should read the ECMA-262 dialect in Unicode mode).
• The uri-template format rejecting an apostrophe in a literal (it should accept it, per RFC 6570 errata 6937).
• The duration format accepting weeks combined with a time part, such as P1WT1H (it should reject it).
• Stack overflow compiling unevaluatedProperties or unevaluatedItems beside a $ref that cycles back to the node, written as #, through its $id, or through a chain of definitions.

Performance

• Building unevaluatedProperties or unevaluatedItems over a deep allOf or $ref chain costs its depth instead of its square.

[0.50.1] - 2026-08-22

Changed

• CanonicalSchema::satisfiability answers Yes for a string whose pattern or format a matching value can be built from.
• CanonicalSchema::satisfiability answers No where a format takes no string of the length the schema asks for.

Fixed

• CanonicalSchema::negate taking apart a union that reads a definition through its own if, so a schema and its negation shared a value.
• CanonicalSchema::subtract dropping a Draft 4 array member an element demand partly takes.
• CanonicalSchema::covers answering Yes where a Draft 4 element demand refuses a member.
• A string schema whose maxLength is 0 keeping a pattern, format, or content facet unread, so the same constraints written in one object and written as an allOf reached different canonical forms.

Performance

• not over a wide object schema costs its branch count instead of its square.
• not over an object schema is linear in its property count, not quadratic.
• not over an object schema with additionalProperties: false no longer costs cubic time in its property count.

... (truncated)

Commits

• b7fd606 chore(rust): Release 0.51.0
• b225a20 fix: Stack overflow compiling unevaluatedProperties or unevaluatedItems b...
• df15d19 build(deps): bump crates/jsonschema/tests/suite
• df8b81c fix: Misc format fixes
• 38056c7 feat: ValidationOptions::with_vocabulary and the vocabularies attribute o...
• 31d52b2 fix: The uniqueItems length ceiling not reading an items or contains sc...
• 5993cf1 chore(ruby): Release 0.50.1
• e04ecc6 build(ruby): Exclude arm-linux-musl
• 1fc21b9 chore(python): Release 0.50.1
• 60a563d chore(rust): Release 0.50.1
• Additional commits viewable in compare view

Updates ref-cast from 1.0.26 to 1.0.27

Release notes

Sourced from ref-cast's releases.

1.0.27

• Suppress let_underscore_must_use clippy restriction in generated code (#56)

Commits

• 971b905 Release 1.0.27
• cdb22ef Merge pull request #56 from dtolnay/letunderscoremustuse
• 88b044f Suppress let_underscore_must_use clippy restriction
• f5224c5 Reproduce issue 55
• 6815484 Raise minimum tested compiler to rust 1.88
• afdc4be Update ui test suite to nightly-2026-07-25
• ffb805e Update ui tests for version 1.0.26
• See full diff in compare view

Updates syn from 3.0.3 to 3.0.4

Release notes

Sourced from syn's releases.

3.0.4

• Allow safe fn in impl Parse for ForeignItemFn (#2078)

Commits

• b5d62a6 Release 3.0.4
• abf019c Merge pull request #2078 from dtolnay/foreginitemfn
• d454333 Allow safe fn in impl Parse for ForeignItemFn
• 8011b1c Update test suite to nightly-2026-08-18
• 56a8d83 Raise rayon thread size for tests
• f2c5c50 Ignore assert_is_empty pedantic clippy lint
• 0eba76d Update test suite to nightly-2026-08-05
• baaebce Update test suite to nightly-2026-07-25
• b886a38 Update test suite to nightly-2026-07-24
• 3c41416 Update test suite to nightly-2026-07-23
• 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