kjuulh/cibus-backend
1
0
Fork 0
Code Issues 1 Pull Requests Packages Projects Releases Wiki Activity

fix(deps): update rust crate anyhow to 1.0.66 - autoclosed #2

Closed
kjuulh wants to merge 1 commits from renovate/anyhow-1.x into main
pull from: renovate/anyhow-1.x
merge into: kjuulh:main
Conversation 0 Commits 1 Files Changed 2 +3 -3
kjuulh commented 2022-10-25 23:08:50 +02:00
Owner
Copy Link

This PR contains the following updates:

Package Type Update Change
anyhow dependencies patch 1.0.60 -> 1.0.66

Release Notes

dtolnay/anyhow

v1.0.66

  • Reduce unhelpful backtrace frames in backtraces captured during a context call (#​279)

v1.0.65

v1.0.64

  • Correctly propagate Backtrace when using #[source] anyhow::Error with thiserror crate (#​231)

v1.0.63

v1.0.62

  • Fix extra rebuilding when interleaving command-line cargo invocations with IDE builds (#​261)

v1.0.61

  • Work around rust-analyzer builds poisoning all subsequent command-line cargo builds (#​252)

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled due to failing status checks.

♻ 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, click this checkbox.

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [anyhow](https://github.com/dtolnay/anyhow) | dependencies | patch | `1.0.60` -> `1.0.66` | --- ### Release Notes <details> <summary>dtolnay/anyhow</summary> ### [`v1.0.66`](https://github.com/dtolnay/anyhow/releases/tag/1.0.66) - Reduce unhelpful backtrace frames in backtraces captured during a `context` call ([#&#8203;279](https://github.com/dtolnay/anyhow/issues/279)) ### [`v1.0.65`](https://github.com/dtolnay/anyhow/releases/tag/1.0.65) - <code>impl <a href="https://doc.rust-lang.org/std/any/trait.Provider.html">Provider</a> for anyhow::Error</code> ### [`v1.0.64`](https://github.com/dtolnay/anyhow/releases/tag/1.0.64) - Correctly propagate Backtrace when using `#[source] anyhow::Error` with [thiserror](https://github.com/dtolnay/thiserror) crate ([#&#8203;231](https://github.com/dtolnay/anyhow/issues/231)) ### [`v1.0.63`](https://github.com/dtolnay/anyhow/releases/tag/1.0.63) - Expose backtraces via the new "generic member access" API on the Error trait (https://github.com/rust-lang/rust/issues/99301, https://github.com/rust-lang/rust/issues/96024) ### [`v1.0.62`](https://github.com/dtolnay/anyhow/releases/tag/1.0.62) - Fix extra rebuilding when interleaving command-line `cargo` invocations with IDE builds ([#&#8203;261](https://github.com/dtolnay/anyhow/issues/261)) ### [`v1.0.61`](https://github.com/dtolnay/anyhow/releases/tag/1.0.61) - Work around rust-analyzer builds poisoning all subsequent command-line cargo builds ([#&#8203;252](https://github.com/dtolnay/anyhow/issues/252)) </details> --- ### Configuration 📅 **Schedule**: At any time (no schedule defined). 🚦 **Automerge**: Disabled due to failing status checks. ♻ **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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, click this checkbox. --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).
kjuulh added 1 commit 2022-10-25 23:08:51 +02:00
fix(deps): update rust crate anyhow to 1.0.66
Some checks failed
continuous-integration/drone/pr Build is failing
Details
continuous-integration/drone/push Build is failing
Details
53e3217d66
kjuulh changed title from fix(deps): update rust crate anyhow to 1.0.66 to fix(deps): update rust crate anyhow to 1.0.66 - autoclosed 2022-10-26 18:00:31 +02:00
kjuulh closed this pull request 2022-10-26 18:00:31 +02:00
Some checks failed
continuous-integration/drone/pr Build is failing
Details
continuous-integration/drone/push Build is failing
Details

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: kjuulh/cibus-backend#2
No description provided.
Delete Branch "renovate/anyhow-1.x"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?