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

chore(deps): Update Rust crate cargo_metadata to 0.19 - autoclosed #851

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 1, 2025

This PR contains the following updates:

Package Type Update Change
cargo_metadata dependencies minor 0.18 -> 0.19

Release Notes

oli-obk/cargo_metadata (cargo_metadata)

v0.19.1

Compare Source

v0.19.0

Compare Source

Added
  • Re-exported semver crate directly.
  • Added implementation of std::ops::Index<&PackageId> for Resolve.
  • Added pub fn is_kind(&self, name: TargetKind) -> bool to Target.
  • Added derived implementations of PartialEq, Eq and Hash for Metadata and its members' types.
  • Added default fields to PackageBuilder.
  • Added pub fn new(name:version:id:path:) -> Self to PackageBuilder for providing all required fields upfront.
Changed
  • Bumped MSRV from 1.42.0 to 1.56.0.
  • Made parse_stream more versatile by accepting anything that implements Read.
  • Converted TargetKind and CrateType to an enum representation.
Removed
  • Removed re-exports for BuildMetadata and Prerelease from semver crate.
  • Removed .is_lib(…), .is_bin(…), .is_example(…), .is_test(…), .is_bench(…), .is_custom_build(…), and .is_proc_macro(…) from Target (in favor of adding .is_kind(…)).
Fixed
  • Added missing manifest_path field to Artifact. Fixes #​187.

Configuration

📅 Schedule: Branch creation - "before 5am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).

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

Rebasing: Whenever PR becomes conflicted, 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 Jan 1, 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: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path Cargo.toml --package [email protected] --precise 0.19.1
    Updating crates.io index
error: failed to select a version for the requirement `cargo_metadata = "^0.18"`
candidate versions found which didn't match: 0.19.1
location searched: crates.io index
required by package `clap-cargo v0.14.1`
    ... which satisfies dependency `clap-cargo = "^0.14.0"` (locked to 0.14.1) of package `cargo-release v0.25.15 (/tmp/renovate/repos/github/crate-ci/cargo-release)`

@epage epage force-pushed the renovate/cargo_metadata-0.x branch 2 times, most recently from e1b11d8 to 7ec9ff0 Compare January 2, 2025 19:05
@renovate renovate bot force-pushed the renovate/cargo_metadata-0.x branch from 7ec9ff0 to 7dfe06c Compare January 2, 2025 19:05
@renovate renovate bot changed the title chore(deps): Update Rust crate cargo_metadata to 0.19 chore(deps): Update Rust crate cargo_metadata to 0.19 - autoclosed Jan 2, 2025
@renovate renovate bot closed this Jan 2, 2025
@renovate renovate bot deleted the renovate/cargo_metadata-0.x branch January 2, 2025 19:13
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