Update lru requirement from 0.14 to 0.15

[dependabot]

Updates the requirements on lru to permit the latest version.

Changelog

Sourced from lru's changelog.

v0.15.0 - 2025-06-26

• Return bool from promote and demote to indicate whether key was found.

v0.14.0 - 2025-04-12

• Use NonZeroUsize::MAX instead of unwrap(), and update MSRV to 1.70.0.

v0.13.0 - 2025-01-27

• Add peek_mru and pop_mru methods, upgrade dependency on hashbrown to 0.15.2, and update MSRV to 1.65.0.

v0.12.5 - 2024-10-30

• Upgrade hashbrown dependency to 0.15.

v0.12.4 - 2024-07-30

• Add methods that take a reference to the key that should be inserted.

v0.12.3 - 2024-02-24

• Add get_key_value_mut method.

v0.12.2 - 2024-01-28

• Add clone method.

v0.12.1 - 2023-11-21

• Add get_key_value method.

v0.12.0 - 2023-10-03

• Add lifetime specifier to try_get_or_insert_mut.
• Add BuildHasher trait bound to Debug for LruCache.

v0.11.1 - 2023-09-05

• Add try_get_or_insert_mut method.

v0.11.0 - 2023-07-11

• Update dependency on hashbrown to 0.14 and update MSRV to 1.64.0.

v0.10.1 - 2023-06-29

• Add try_get_or_insert method.

v0.10.0 - 2023-03-04

... (truncated)

Commits

• 514cc47 Merge pull request #213 from jeromefroe/jerome/prepare-0-15-0-release
• c1e43af Prepare 0.15.0 release
• 9903725 Merge pull request #212 from levkk/levkk-promote
• 11d5b77 Return true/false for promote/demote
• 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 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)

---

Important

Update lru dependency to version 0.15 in stateflow/Cargo.toml to utilize new features.

• Dependencies:
  • Update lru version from 0.14 to 0.15 in stateflow/Cargo.toml.
• Features:
  • Utilize new lru features: promote and demote return a boolean indicating key presence.

^{This description was created by for fe3cb69. You can customize this summary. It will automatically update as commits are pushed.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to fe3cb69 in 55 seconds. Click for details.

• Reviewed 13 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 1 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. stateflow/Cargo.toml:19

• Draft comment:
  Dependency update to lru 0.15 looks correct. Note that promote/demote methods now return a bool. Ensure any code using these functions is updated accordingly.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 0% vs. threshold = 50% The comment violates several rules: 1) It's about dependency changes which we're told to ignore 2) It asks the author to "ensure" something which is a rule violation 3) It's speculative - we don't know if the code even uses promote/demote methods 4) Without seeing the actual code using this dependency, we can't verify if this is actually an issue. Maybe this is an important breaking change that could cause runtime errors if not addressed? Maybe we should keep it as a safety measure? No - our rules explicitly state to ignore dependency-related comments. Build errors or tests would catch any API incompatibilities. We don't have enough context to verify if this is even relevant. Delete this comment as it violates multiple rules - it's about dependencies, uses "ensure", and is speculative without concrete evidence of an issue.

Workflow ID: wflow_rbBKNrcou2SXtweu

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[dependabot]

Superseded by #26.