build(deps): bump krates from 0.11.0 to 0.15.3

[dependabot]

Bumps krates from 0.11.0 to 0.15.3.

Release notes

Sourced from krates's releases.

Release 0.15.3

Fixed

• PR#63 resolved #62 which was a bug introduced in PR#61

Release 0.15.2

Fixed

• PR#61 resolved #60 by refactoring the building of the crate graph to do its own crate and feature resolution to properly handle pruning based on the user's desires.

Release 0.15.1

Added

• PR#59 added Krates::krates_filtered, allowing filtering of crates based upon their edge kinds.

Release 0.15.0

Changed

• PR#58 removed the prefer-index feature, which brought in tame-index, in favor of just letting the user provide a callback that can be used to gather index information, freeing this crate from dependency issues and allowing downstream crates more flexibility.

Release 0.14.1

Changed

• PR#57 bumped tame-index to 0.4.

Release 0.14.0

Changed

• PR#55 and PR#56 replaced crates-index with tame-index
• PR#56 changed Krates::lock_path -> Krates::workspace_root, which can then be joined with Cargo.lock to get the same path, but workspace root is more generally useful.

Release 0.13.1

Fixed

• PR#54 fixed an issue where the crates.io index was unconditionally opened, and synced, if the prefer-index feature was enabled, causing long stalls if using the crates.io sparse index instead.

Release 0.13.0

Changed

• PR#53 updated cfg-expr to 0.14 and crates-index to 0.19.

Fixed

• PR#53 added support for using the HTTP sparse index for crates.io. If the sparse index was enabled and there wasn't a regular git index (for example, if you use dtolnay/rust-toolchain@stable in your CI) this would cause no index to be used to fix crate features if prefer-index was enabled.

Release 0.12.6

Changed

• PR#52 updated cfg-expr to 0.12.
• PR#52 changed Krates::search_matches and Krates::search_by_name to use impl Into<String> for the name to search, so that the lifetime of it is not paired with the graph itself.

Release 0.12.5

Fixed

• PR#51 resolved #50 by no longer treating the feature set in the index as authoritative, but rather just merging in the keys that were not already located in the feature set from the crate itself. This would mean that features that are present in both but with different sub-features from the index will now be lost, but that can be fixed later if it is actually an issue.

Release 0.12.4

Fixed

• PR#49 resolved #48 by not entering into an infinite loop in the presence of cyclic features. Oops.

Release 0.12.3

... (truncated)

Changelog

Sourced from krates's changelog.

[0.15.3] - 2024-01-12

Fixed

• PR#63 resolved #62 which was a bug introduced in PR#61

[0.15.2] - 2024-01-12

Fixed

• PR#61 resolved #60 by refactoring the building of the crate graph to do its own crate and feature resolution to properly handle pruning based on the user's desires.

[0.15.1] - 2023-09-03

Added

• PR#59 added Krates::krates_filtered, allowing filtering of crates based upon their edge kinds.

[0.15.0] - 2023-08-23

Changed

• PR#58 removed the prefer-index feature, which brought in tame-index, in favor of just letting the user provide a callback that can be used to gather index information, freeing this crate from dependency issues and allowing downstream crates more flexibility.

[0.14.1] - 2023-08-21

Changed

• PR#57 bumped tame-index to 0.4.

[0.14.0] - 2023-07-25

Changed

• PR#55 and PR#56 replaced crates-index with tame-index
• PR#56 changed Krates::lock_path -> Krates::workspace_root, which can then be joined with Cargo.lock to get the same path, but workspace root is more generally useful.

[0.13.1] - 2023-06-13

Fixed

• PR#54 fixed an issue where the crates.io index was unconditionally opened, and synced, if the prefer-index feature was enabled, causing long stalls if using the crates.io sparse index instead.

[0.13.0] - 2023-04-04

Changed

• PR#53 updated cfg-expr to 0.14 and crates-index to 0.19.

Fixed

• PR#53 added support for using the HTTP sparse index for crates.io. If the sparse index was enabled and there wasn't a regular git index (for example, if you use dtolnay/rust-toolchain@stable in your CI) this would cause no index to be used to fix crate features if prefer-index was enabled.

[0.12.6] - 2022-11-25

Changed

• PR#52 updated cfg-expr to 0.12.
• PR#52 changed Krates::search_matches and Krates::search_by_name to use impl Into<String> for the name to search, so that the lifetime of it is not paired with the graph itself.

[0.12.5] - 2022-11-08

Fixed

• PR#51 resolved #50 by no longer treating the feature set in the index as authoritative, but rather just merging in the keys that were not already located in the feature set from the crate itself. This would mean that features that are present in both but with different sub-features from the index will now be lost, but that can be fixed later if it is actually an issue.

[0.12.4] - 2022-11-02

Fixed

• PR#49 resolved #48 by not entering into an infinite loop in the presence of cyclic features. Oops.

[0.12.3] - 2022-11-01

... (truncated)

Commits

• f35dd5e Release 0.15.3
• 97a9756 Update CHANGELOG
• 02d1a88 Fix feature name => crate (#63)
• 36b7a7a Release 0.15.2
• 7ddbded Update CHANGELOG
• b583d96 Fix crate pruning (#61)
• 96af626 Release 0.15.1
• b7e4dbf Add support for filtering built graphs (#59)
• 504006f Release 0.15.0
• 4eb3233 Update CHANGELOG
• 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #502.