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.

Sign up for GitHub

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

Jump to bottom

fix(deps): update rust crate anyhow to v1.0.97 #122

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

fix(deps): update rust crate anyhow to v1.0.97 #122

wants to merge 1 commit into from
+3 −3

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 5, 2024 •
edited
Loading

This PR contains the following updates:

Package Type Update Change
anyhow dependencies patch 1.0.58 -> 1.0.97

Release Notes

dtolnay/anyhow (anyhow)

v1.0.97

Compare Source

  • Documentation improvements

v1.0.96

Compare Source

  • Documentation improvements

v1.0.95

Compare Source

v1.0.94

Compare Source

  • Documentation improvements

v1.0.93

Compare Source

  • Update dev-dependencies to thiserror v2

v1.0.92

Compare Source

  • Support Rust 1.82's &raw const and &raw mut syntax inside ensure! (#​390)

v1.0.91

Compare Source

  • Ensure OUT_DIR is left with deterministic contents after build script execution (#​388)

v1.0.90

Compare Source

  • Documentation improvements

v1.0.89

Compare Source

  • Make anyhow::Error's UnwindSafe and RefUnwindSafe impl consistently available between versions of Rust newer and older than 1.72 (#​386)

v1.0.88

Compare Source

  • Documentation improvements

v1.0.87

Compare Source

  • Support more APIs, including Error::new and Error::chain, in no-std mode on Rust 1.81+ (#​383)

v1.0.86

Compare Source

  • Fix parse error in ensure! with non-literal after minus sign (#​373)

v1.0.85

Compare Source

  • Improve ensure! macro's rules to unblock some rustc pretty-printer improvements (#​368, #​371)

v1.0.84

Compare Source

  • Disallow calling ensure! through a Not impl for a type that is not bool (#​367)

v1.0.83

Compare Source

  • Integrate compile-time checking of cfgs (#​363)

v1.0.82

Compare Source

  • Documentation improvements

v1.0.81

Compare Source

  • Make backtrace support available when using -Dwarnings (#​354)

v1.0.80

Compare Source

  • Fix unused_imports warnings when compiled by rustc 1.78

v1.0.79

Compare Source

  • Work around improperly cached build script result by sccache (#​340)

v1.0.78

Compare Source

  • Reduce spurious rebuilds under RustRover IDE when using a nightly toolchain (#​337)

v1.0.77

Compare Source

v1.0.76

Compare Source

  • Opt in to unsafe_op_in_unsafe_fn lint (#​329)

v1.0.75

Compare Source

v1.0.74

Compare Source

v1.0.73

Compare Source

v1.0.72

Compare Source

  • Documentation improvements

v1.0.71

Compare Source

  • Documentation improvements

v1.0.70

Compare Source

  • Update syn dependency to 2.x

v1.0.69

Compare Source

  • Documentation improvements

v1.0.68

Compare Source

  • Opt out of -Zrustdoc-scrape-examples on docs.rs for now

v1.0.67

Compare Source

  • Improve the backtrace captured when context() is used on an Option (#​280)

v1.0.66

Compare Source

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

v1.0.65

Compare Source

v1.0.64

Compare Source

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

v1.0.63

Compare Source

v1.0.62

Compare Source

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

v1.0.61

Compare Source

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

v1.0.60

Compare Source

  • Propagate --target to rustc invocation when deciding about backtrace support (#​249, thanks @​RalfJung)

v1.0.59

Compare Source

  • Update crates.io metadata to include no-std category

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

@renovate Renovate
Copy link
Contributor Author

renovate bot commented May 5, 2024 •
edited
Loading

⚠ Artifact update problem

Renovate failed to update artifacts 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: mvsqlite/Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path mvsqlite/Cargo.toml --package [email protected] --precise 1.0.83
warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions
error: package ID specification `[email protected]` did not match any packages
Did you mean one of these?

  [email protected]
File name: mvfs/Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path mvfs/Cargo.toml --package [email protected] --precise 1.0.83
warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions
error: package ID specification `[email protected]` did not match any packages
Did you mean one of these?

  [email protected]

@renovate renovate bot force-pushed the renovate/anyhow-1.x-lockfile branch from f071805 to 9830661 Compare May 6, 2024 22:34
@renovate renovate bot changed the title fix(deps): update rust crate anyhow to v1.0.82 fix(deps): update rust crate anyhow to v1.0.83 May 6, 2024
@renovate renovate bot force-pushed the renovate/anyhow-1.x-lockfile branch from 9830661 to 561e9d0 Compare May 18, 2024 00:01
@renovate renovate bot changed the title fix(deps): update rust crate anyhow to v1.0.83 fix(deps): update rust crate anyhow to v1.0.85 May 18, 2024
@renovate renovate bot force-pushed the renovate/anyhow-1.x-lockfile branch from 561e9d0 to f57507d Compare May 18, 2024 16:08
@renovate renovate bot changed the title fix(deps): update rust crate anyhow to v1.0.85 fix(deps): update rust crate anyhow to v1.0.86 May 18, 2024
@renovate renovate bot changed the title fix(deps): update rust crate anyhow to v1.0.86 fix(deps): update rust crate anyhow to v1.0.87 Sep 6, 2024
@renovate renovate bot changed the title fix(deps): update rust crate anyhow to v1.0.87 fix(deps): update rust crate anyhow to v1.0.88 Sep 11, 2024
@renovate renovate bot changed the title fix(deps): update rust crate anyhow to v1.0.88 fix(deps): update rust crate anyhow to v1.0.89 Sep 15, 2024
@renovate renovate bot force-pushed the renovate/anyhow-1.x-lockfile branch from f57507d to 9a16c4d Compare September 16, 2024 11:08
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Sep 16, 2024 •
edited
Loading

⚠️ Artifact update problem

Renovate failed to update artifacts 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: mvfs/Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path mvfs/Cargo.toml --package [email protected] --precise 1.0.97
warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions
error: package ID specification `[email protected]` did not match any packages
Did you mean one of these?

  [email protected]
File name: mvsqlite/Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path mvsqlite/Cargo.toml --package [email protected] --precise 1.0.97
warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions
error: package ID specification `[email protected]` did not match any packages
Did you mean one of these?

  [email protected]

@renovate renovate bot force-pushed the renovate/anyhow-1.x-lockfile branch from 9a16c4d to 3befc0f Compare October 19, 2024 05:45
@renovate renovate bot changed the title fix(deps): update rust crate anyhow to v1.0.89 fix(deps): update rust crate anyhow to v1.0.90 Oct 19, 2024
@renovate renovate bot force-pushed the renovate/anyhow-1.x-lockfile branch from 3befc0f to 0d2a336 Compare October 22, 2024 19:21
@renovate renovate bot changed the title fix(deps): update rust crate anyhow to v1.0.90 fix(deps): update rust crate anyhow to v1.0.91 Oct 22, 2024
@renovate renovate bot force-pushed the renovate/anyhow-1.x-lockfile branch from 0d2a336 to 742ebaa Compare November 1, 2024 06:26
@renovate renovate bot changed the title fix(deps): update rust crate anyhow to v1.0.91 fix(deps): update rust crate anyhow to v1.0.92 Nov 1, 2024
@renovate renovate bot force-pushed the renovate/anyhow-1.x-lockfile branch from 742ebaa to 2fe07ad Compare November 6, 2024 05:21
@renovate renovate bot changed the title fix(deps): update rust crate anyhow to v1.0.92 fix(deps): update rust crate anyhow to v1.0.93 Nov 6, 2024
@renovate renovate bot force-pushed the renovate/anyhow-1.x-lockfile branch from 2fe07ad to 3bc864c Compare December 3, 2024 23:33
@renovate renovate bot changed the title fix(deps): update rust crate anyhow to v1.0.93 fix(deps): update rust crate anyhow to v1.0.94 Dec 3, 2024
@renovate renovate bot force-pushed the renovate/anyhow-1.x-lockfile branch from 3bc864c to 098750a Compare December 22, 2024 14:30
@renovate renovate bot changed the title fix(deps): update rust crate anyhow to v1.0.94 fix(deps): update rust crate anyhow to v1.0.95 Dec 22, 2024
@renovate renovate bot force-pushed the renovate/anyhow-1.x-lockfile branch from 098750a to 6422a2d Compare February 20, 2025 06:57
@renovate renovate bot changed the title fix(deps): update rust crate anyhow to v1.0.95 fix(deps): update rust crate anyhow to v1.0.96 Feb 20, 2025
@renovate renovate bot force-pushed the renovate/anyhow-1.x-lockfile branch from 6422a2d to fb4bf98 Compare March 3, 2025 06:14
@renovate renovate bot changed the title fix(deps): update rust crate anyhow to v1.0.96 fix(deps): update rust crate anyhow to v1.0.97 Mar 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants