Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Aug 15, 2025

This PR contains the following updates:

Package Type Update Change
human-panic dependencies patch 2.0.22.0.6

Release Notes

rust-cli/human-panic (human-panic)

v2.0.6

Compare Source

Features
  • Added Metadata::repository as a fallback for Metadata::homepage

v2.0.5

Compare Source

Performance
  • Improve build times on some platforms by changing from os_info to sysinfo

v2.0.4

Compare Source

v2.0.3

Compare Source

Internal
  • Update toml

Configuration

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

🚦 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.

🔕 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.

@renovate renovate bot changed the title fix(deps): update rust crate human-panic to v2.0.3 chore(deps): update rust crate human-panic to v2.0.3 Sep 25, 2025
@renovate renovate bot force-pushed the renovate/human-panic-2.x-lockfile branch from 67efa6c to 2533cb0 Compare October 28, 2025 20:09
@renovate renovate bot changed the title chore(deps): update rust crate human-panic to v2.0.3 chore(deps): update rust crate human-panic to v2.0.4 Oct 28, 2025
@renovate renovate bot changed the title chore(deps): update rust crate human-panic to v2.0.4 chore(deps): update rust crate human-panic to v2.0.5 Dec 26, 2025
@renovate renovate bot force-pushed the renovate/human-panic-2.x-lockfile branch from 2533cb0 to f188198 Compare December 26, 2025 17:48
@renovate renovate bot changed the title chore(deps): update rust crate human-panic to v2.0.5 chore(deps): update rust crate human-panic to v2.0.6 Dec 29, 2025
@renovate
Copy link
Contributor Author

renovate bot commented Dec 29, 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 human-panic@2.0.2 --precise 2.0.6
    Updating crates.io index
error: failed to select a version for `backtrace`.
    ... required by package `color-eyre v0.6.3`
    ... which satisfies dependency `color-eyre = "^0.6.3"` (locked to 0.6.3) of package `dnote-tui v0.5.10 (/tmp/renovate/repos/github/deepanchal/dnote-tui)`
versions that meet the requirements `^0.3.48` are: 0.3.71, 0.3.76, 0.3.75, 0.3.74, 0.3.73, 0.3.72, 0.3.69, 0.3.68, 0.3.67, 0.3.66, 0.3.65, 0.3.64, 0.3.63, 0.3.62, 0.3.61, 0.3.60, 0.3.59, 0.3.58, 0.3.57, 0.3.56, 0.3.55, 0.3.54, 0.3.53, 0.3.52, 0.3.51, 0.3.50, 0.3.49, 0.3.48

package `color-eyre` depends on `backtrace` with feature `gimli-symbolize` but `backtrace` does not have that feature.
 package `backtrace` does have feature `gimli-symbolize`


all possible versions conflict with previously selected packages.

  previously selected package `backtrace v0.3.76`
    ... which satisfies dependency `backtrace = "^0.3.48"` of package `color-eyre v0.6.3`
    ... which satisfies dependency `color-eyre = "^0.6.3"` (locked to 0.6.3) of package `dnote-tui v0.5.10 (/tmp/renovate/repos/github/deepanchal/dnote-tui)`

failed to select a version for `backtrace` which could resolve this conflict

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