Update rust - all minor and patch updates

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
clap	workspace.dependencies	patch	4.4.12 -> 4.4.13
pest (source)	workspace.dependencies	patch	2.7.5 -> 2.7.6
pest_derive (source)	workspace.dependencies	patch	2.7.5 -> 2.7.6
serde (source)	workspace.dependencies	patch	1.0.194 -> 1.0.195
strum	dependencies	minor	0.24.1 -> 0.25.0
strum_macros	dependencies	minor	0.24.3 -> 0.25.3

---

Release Notes

clap-rs/clap (clap)

v4.4.13

Compare Source

Documentation

• Fix link to structopt migration guide

pest-parser/pest (pest)

v2.7.6

Compare Source

What's Changed

• perf: use str instead of Cow to reduce Token size by @​sssooonnnggg in https://github.com/pest-parser/pest/pull/958
• bump versions + minor clippy fixes by @​tomtau in https://github.com/pest-parser/pest/pull/959

New Contributors

• @​sssooonnnggg made their first contribution in https://github.com/pest-parser/pest/pull/958

Full Changelog: pest-parser/pest@v2.7.5...v2.7.6

Warning: Semantic Versioning

Note that the node tag feature in 2.6.0 was a technically semver-breaking change even though it is a backwards-compatible / non-breaking change in the meta-grammar. There may be similar non-breaking changes to the meta-grammar between minor versions in the future. These non-breaking changes, however, may translate into semver-breaking changes due to the additional variants propagated from the generated Rule enum.

This new feature caused issues in some Cargo version resolution situations where Cargo mixed different versions of pest dependencies. For this reason, these "grammar non-breaking but semver-breaking" changes are now available only under the "grammar-extras" feature flag. If you would like to use node tags (or other future grammar features), you can do so by enabling this flag on the pest_derive crate in your Cargo.toml:

...
pest_derive = { version = "2.7", features = ["grammar-extras"] }

serde-rs/serde (serde)

v1.0.195

Compare Source

• Prevent remote definitions of tuple struct or tuple variant from triggering dead_code warning (#​2671)

Peternator7/strum (strum)

v0.25.0

Breaking Changes

• #​261 Upgrade syn dependency to version 2. This bumps the msrv to
  1.56. It's impractical to maintain a package where a core dependency of the ecosystem has a different msrv than this one.

• 270 Change the to_string behavior when using default. Now, when
  using default, the display method will return the display version of the value contained in the enum rather than
  the name of the variant.

  #[derive(strum::Display)]
  enum Color {
    Red,
    Blue,
    Green,
    #[strum(default)]
    Other(String)
  }
  
  fn main() {
    // This used to print "Other", now it prints "Purple"
    assert_eq!(Color::Other("Purple".to_string()).to_string(), "Purple");
  }

  If you want the old behavior, you can use the to_string attribute to override this behavior. See the PR for an example.

• 268 Update the behavior of EnumCount to exclude variants that are
  disabled. This is a breaking change, but the behavior makes it more consistent with other methods.

New Features

• #​257 This PR adds the EnumIs macro that automatically implements
  is_{variant_name} methods for each variant.

  #[derive(EnumIs)]
  enum Color {
      Red,
      Blue,
      Green,
  }
  
  #[test]
  fn simple_test() {
      assert!(Color::Red.is_red());
  }

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "after 10pm every weekday,before 5am every weekday,every weekend" in timezone Europe/London.

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, 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 has been generated by Mend Renovate. View repository job log here.

[github-actions]

This PR updates the following pallets - they may also require updates to their extrinsic weights:
process-validation simple-nft symmetric-key

For the author and any reviewers:

• consider whether the changes could significantly affect the weight of any extrinsics
• consider whether benchmarks need updating to correctly cover weight variations over inputs

For a guide on running benchmarks to update weights see calculating weights

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path runtime/types/Cargo.toml --package [email protected] --precise 0.25.0
    Updating crates.io index
error: failed to select a version for the requirement `strum = "^0.24.1"`
candidate versions found which didn't match: 0.25.0
location searched: crates.io index
required by package `sp-keyring v24.0.0 (https://github.com/paritytech/polkadot-sdk.git?branch=release-polkadot-v1.5.0#789ffb66)`
    ... which satisfies git dependency `sp-keyring` (locked to 24.0.0) of package `dscp-node v10.0.0 (/tmp/renovate/repos/github/digicatapult/dscp-node/node)`
perhaps a crate was updated and forgotten to be re-vendored?

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.