chore: bump the patch group with 6 updates

[dependabot]

Bumps the patch group with 6 updates:

Package	From	To
clap_complete	4.6.8	4.6.9
ignore	0.4.31	0.4.33
open	5.4.0	5.4.1
similar	3.1.1	3.1.2
jsonschema	0.49.5	0.49.6
vergen-gitcl	10.0.1	10.0.2

Updates clap_complete from 4.6.8 to 4.6.9

Commits

• 715b812 chore: Release
• 89e6e9b docs: Update changelog
• 3918cb4 Merge pull request #6468 from sjh9714/fix-bash-posix-fn-name
• 526c819 Merge pull request #6469 from latent-9/docs/fix-derive-reference-link
• b2bd685 docs(clap_derive): Fix derive reference link
• ecee8a4 fix(complete): Name the function after fn_name
• 6dd2e5a test(complete): Show POSIX bash will not source
• 4684d7a chore: Release
• 51d50ad docs: Update changelog
• 3bc3622 Merge pull request #6457 from bl4ck4t/master
• Additional commits viewable in compare view

Updates ignore from 0.4.31 to 0.4.33

Commits

• 3fce3b5 ignore-0.4.33
• 5055264 globset-0.4.20
• 020687a ignore,globset: increase pool capacity
• 5ed408e ignore-0.4.32
• 435f59f ignore: skip loading unreachable ignore files
• f9c05a9 index: remove incorrect README
• 8372866 index: add some initial indexing scaffolding
• d99ac34 core: add index module
• 2ed0c00 flags: disable many flags when indexing is enabled
• See full diff in compare view

Updates open from 5.4.0 to 5.4.1

Release notes

Sourced from open's releases.

v5.4.1

Bug Fixes

• Forward WSL targets to PowerShell to make open actually work there

  Opening a URL from WSL failed because the Windows process did not receive OPEN_RS_TARGET, even though it was present in the Linux command environment. The failure reproduces with cargo run -- https://google.com on Ubuntu under WSL, where Start-Process receives a null FilePath and exits unsuccessfully.

  Add OPEN_RS_TARGET to WSLENV so WSL interop forwards the target into the PowerShell environment. Preserve existing WSLENV entries and their flags, while keeping the PowerShell command fixed so targets remain data rather than shell code.

  Validated with focused WSL tests, the all-features test suite, rustfmt, Clippy with warnings denied, and an end-to-end cargo run from WSL.

Commit Statistics

• 1 commit contributed to the release.
• 24 days passed between releases.
• 1 commit was understood as conventional.
• 1 unique issue was worked on: #128

Commit Details

• #128
  • Forward WSL targets to PowerShell to make open actually work there (96fa673)

Changelog

Sourced from open's changelog.

5.4.1 (2026-08-05)

Bug Fixes

• Forward WSL targets to PowerShell to make open actually work there

  Opening a URL from WSL failed because the Windows process did not receive OPEN_RS_TARGET, even though it was present in the Linux command environment. The failure reproduces with cargo run -- https://google.com on Ubuntu under WSL, where Start-Process receives a null FilePath and exits unsuccessfully.

  Add OPEN_RS_TARGET to WSLENV so WSL interop forwards the target into the PowerShell environment. Preserve existing WSLENV entries and their flags, while keeping the PowerShell command fixed so targets remain data rather than shell code.

  Validated with focused WSL tests, the all-features test suite, rustfmt, Clippy with warnings denied, and an end-to-end cargo run from WSL.

Commit Statistics

• 1 commit contributed to the release.
• 24 days passed between releases.
• 1 commit was understood as conventional.
• 1 unique issue was worked on: #128

Commit Details

• #128
  • Forward WSL targets to PowerShell to make open actually work there (96fa673)

Commits

• e548a4e Release open v5.4.1
• 96fa673 fix: Forward WSL targets to PowerShell to make open actually work there (#128)
• See full diff in compare view

Updates similar from 3.1.1 to 3.1.2

Changelog

Sourced from similar's changelog.

3.1.2

• Fixed Algorithm::Lcs deadline fallback emitting edits twice, which produced out-of-bounds DiffOp ranges and panics when consuming timed-out diffs. #97
• Fixed Algorithm::Lcs reporting identical subranges with zero-based indices instead of preserving the supplied range offsets. #98
• Fixed Algorithm::Lcs and Algorithm::Hunt emitting zero-length delete operations when both inputs are empty. #99

Commits

• 71f0a30 chore(release): prepare 3.1.2
• a0aa51e docs(changelog): document recent fixes
• 5119534 fix(algorithms): omit operations for empty inputs
• 043c907 fix(lcs): preserve indices for equal subranges
• cfad604 fix(lcs): avoid duplicate deadline fallback edits
• See full diff in compare view

Updates jsonschema from 0.49.5 to 0.49.6

Release notes

Sourced from jsonschema's releases.

[Python] Release 0.49.6

Added

• Canonicalization of a negated uniqueItems, where the complement demands a repeated element under the length floor two elements imply.
• Canonicalization of a negated array tuple, where each position's complement stands under the length that reaches it.
• Canonicalization of contains demands sharing no value, where their counts add up into a length floor.
• CanonicalSchema.negate through references, where the complement of the resolved target takes the reference's place.
• Canonicalization of negated propertyNames and additionalProperties, where the complement spells the violating-key demand instead of a not residual.
• Canonicalization of negated additionalProperties under Draft 4, where the violating-key demand spells the closed property map.
• Canonicalization of not a reference, where the complement of the resolved target takes the pointer's place.
• Canonicalization of a negated oneOf, where the complement spells the values no branch admits beside the values two branches share.
• Canonicalization of negated items under Draft 4, where the violating-element demand spells the barred element schema.

Changed

• ArrayView reports distinctness in three states, so an array demanding a repeated element reads apart from one demanding distinct elements.

Fixed

• CanonicalSchema.negate keeping a root self-reference in the complement, where it points at the complement instead of the source.
• An additionalItems that tails no tuple keeping the whole document unmodeled under Draft 2020-12.

[Ruby] Release 0.49.6

Added

• Canonicalization of a negated uniqueItems, where the complement demands a repeated element under the length floor two elements imply.
• Canonicalization of a negated array tuple, where each position's complement stands under the length that reaches it.
• Canonicalization of contains demands sharing no value, where their counts add up into a length floor.
• CanonicalSchema#negate through references, where the complement of the resolved target takes the reference's place.
• Canonicalization of negated propertyNames and additionalProperties, where the complement spells the violating-key demand instead of a not residual.
• Canonicalization of negated additionalProperties under Draft 4, where the violating-key demand spells the closed property map.
• Canonicalization of not a reference, where the complement of the resolved target takes the pointer's place.
• Canonicalization of a negated oneOf, where the complement spells the values no branch admits beside the values two branches share.
• Canonicalization of negated items under Draft 4, where the violating-element demand spells the barred element schema.

Changed

• ArrayView reports distinctness in three states, so an array demanding a repeated element reads apart from one demanding distinct elements.

Fixed

• CanonicalSchema#negate keeping a root self-reference in the complement, where it points at the complement instead of the source.
• An additionalItems that tails no tuple keeping the whole document unmodeled under Draft 2020-12.

[Rust] Release 0.49.6

Added

• Canonicalization of a negated uniqueItems, where the complement demands a repeated element under the length floor two elements imply.
• Canonicalization of a negated array tuple, where each position's complement stands under the length that reaches it.
• Canonicalization of contains demands sharing no value, where their counts add up into a length floor.

... (truncated)

Changelog

Sourced from jsonschema's changelog.

[0.49.6] - 2026-08-06

Added

• Canonicalization of a negated uniqueItems, where the complement demands a repeated element under the length floor two elements imply.
• Canonicalization of a negated array tuple, where each position's complement stands under the length that reaches it.
• Canonicalization of contains demands sharing no value, where their counts add up into a length floor.
• CanonicalSchema::negate through references, where the complement of the resolved target takes the reference's place.
• Canonicalization of negated propertyNames and additionalProperties, where the complement spells the violating-key demand instead of a not residual.
• Canonicalization of negated additionalProperties under Draft 4, where the violating-key demand spells the closed property map.
• Canonicalization of not a reference, where the complement of the resolved target takes the pointer's place.
• Canonicalization of a negated oneOf, where the complement spells the values no branch admits beside the values two branches share.
• Canonicalization of negated items under Draft 4, where the violating-element demand spells the barred element schema.

Changed

• ArrayView reports distinctness in three states, so an array demanding a repeated element reads apart from one demanding distinct elements.

Fixed

• CanonicalSchema::negate keeping a root self-reference in the complement, where it points at the complement instead of the source.
• An additionalItems that tails no tuple keeping the whole document unmodeled under Draft 2020-12.

Commits

• 7888cb4 chore(ruby): Release 0.49.6
• d57a7e0 chore(python): Release 0.49.6
• eaeb5b3 chore(rust): Release 0.49.6
• d87ab9b fix: An additionalItems that tails no tuple keeping the whole document unmo...
• b31c404 feat: Canonicalization of a negated uniqueItems, where the complement deman...
• cbcf755 build(deps): bump crates/jsonschema/tests/suite
• d89a297 build(deps): bump crate-ci/typos from 1.48.0 to 1.49.0
• 8285c96 feat: Canonicalization of a negated array tuple, where each position's comple...
• 05d579c feat: Canonicalization of negated items under Draft 4, where the violating-...
• 8c53ddb feat: Canonicalization of a negated oneOf, where the complement spells the ...
• Additional commits viewable in compare view

Updates vergen-gitcl from 10.0.1 to 10.0.2

Commits

• 8355721 chore(deps): dependency updates and Windows lcov fix (#520)
• ff70eeb chore(msrv): bump MSRV to 1.96.0 (#519)
• 13e7cb6 chore(rake): Rakefile.toml build pipeline and lint updates (#518)
• a39ba61 chore: replace deprecated provenance lints with implicit_provenance_casts (#517)
• 8d9813a chore(rake): tweak macos daily (#516)
• cd4af2a chore: add Rakefile.toml build pipeline and fix doc references (#515)
• 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