Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update rust crate strum to 0.27 #2580

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 9, 2025

This PR contains the following updates:

Package Type Update Change
strum dependencies minor 0.26 -> 0.27

Release Notes

Peternator7/strum (strum)

v0.27.0

Compare Source

Highlights
  • #​407: Display is now correctly derived in [no_std] projects.
  • #​402: EnumIter now implements Send + Sync
  • #​400: EnumTryAs now handles attributes on variant fields correctly.
  • #​398: strum is now on rust 2021
  • #​391: EnumProperties correctly implements get_bool and get_int
    finally. 🎉
  • #​380: FromString now supports 2 additional attributes, parse_error_ty
    and parse_error_fn that can be added to use a custom error type rather than the default strum error message.
    • #​410: These attributes accept a Path rather than a String
      to improve behavior with rust-analyzer.
Breaking Changes
  • #​384: MSRV is now 1.66.1
  • #​391: EnumProperties doesn't provide default implementations anymore.
    This would have required you to manually implement this trait which should be very uncommon.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Copy link
Contributor Author

renovate bot commented Feb 9, 2025

⚠️ 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: backend/Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path backend/tauri/Cargo.toml --package [email protected] --precise 0.27.0
    Updating crates.io index
error: failed to select a version for the requirement `strum = "^0.26.0"`
candidate versions found which didn't match: 0.27.0
location searched: crates.io index
required by package `naga v24.0.0`
    ... which satisfies dependency `naga = "^24.0.0"` (locked to 24.0.0) of package `wgpu-hal v24.0.0`
    ... which satisfies dependency `hal = "^24.0.0"` (locked to 24.0.0) of package `wgpu v24.0.1`
    ... which satisfies dependency `wgpu = "^24.0.0"` (locked to 24.0.1) of package `egui-wgpu v0.31.0`
    ... which satisfies dependency `egui-wgpu = "^0.31.0"` (locked to 0.31.0) of package `eframe v0.31.0`
    ... which satisfies dependency `eframe = "^0.31"` (locked to 0.31.0) of package `nyanpasu-egui v0.1.0 (/tmp/renovate/repos/github/libnyanpasu/clash-nyanpasu/backend/nyanpasu-egui)`
    ... which satisfies path dependency `nyanpasu-egui` (locked to 0.1.0) of package `clash-nyanpasu v0.1.0 (/tmp/renovate/repos/github/libnyanpasu/clash-nyanpasu/backend/tauri)`

@renovate renovate bot force-pushed the renovate/strum-monorepo branch 10 times, most recently from f576f8f to ccfe818 Compare February 10, 2025 01:15
@renovate renovate bot force-pushed the renovate/strum-monorepo branch from ccfe818 to c65c0b9 Compare February 10, 2025 02:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants