Skip to content

chore(deps): update rust crate snafu to v0.8.9#103

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/snafu-0.x-lockfile
Open

chore(deps): update rust crate snafu to v0.8.9#103
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/snafu-0.x-lockfile

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented May 28, 2025

This PR contains the following updates:

Package Type Update Change
snafu dependencies patch 0.8.50.8.9

Release Notes

shepmaster/snafu (snafu)

v0.8.9

Compare Source

Fixed
  • Allow the unstable-provider-api feature to be used in a no_std
    environment, both with and without the alloc feature flag enabled.

v0.8.8

Compare Source

Fixed
  • Gate TryFuture::whatever_context,
    TryFuture::with_whatever_context, TryStream::whatever_context,
    and TryStream::with_whatever_context behind the alloc feature
    flag. This allows SNAFU's future and stream combinators to be used
    in a no_std environment.

  • Only implement GenerateImplicitData and AsBacktrace for Arc
    wrappers when the target platform has access to atomics and Arc.

v0.8.7

Compare Source

Added
  • GenerateImplicitData and AsBacktrace are now implemented for
    Box<T>, Rc<T>, and Arc<T> when T implements the same
    trait. This allows you to use types like Arc<Backtrace> as a
    backtrace field.

v0.8.6

Compare Source

Added
  • A new alloc feature flag has been added as a subset of the
    existing std feature flag. This allows SNAFU to be used in
    environments that have access to an allocator but not the standard
    library.

  • Context selectors may now be explicitly named. This allows
    flexibility in edge cases, but also is understood by rust-analyzer
    to help with renaming context selectors.

Fixed
  • Added #[allow(dead_code)] to the context selector's fail
    method. This works around an issue with the dead_code lint in rare
    usages involving declarative macros and explicit visibility
    qualifiers.
Changed
  • Add top-level documentation on reporting errors using
    #[snafu::report].

  • Show the cfg options that control features on docs.rs.


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 bot force-pushed the renovate/snafu-0.x-lockfile branch from 2201775 to 74d8882 Compare August 20, 2025 22:01
@renovate renovate bot changed the title fix(deps): update rust crate snafu to v0.8.6 fix(deps): update rust crate snafu to v0.8.7 Aug 20, 2025
@renovate renovate bot changed the title fix(deps): update rust crate snafu to v0.8.7 fix(deps): update rust crate snafu to v0.8.8 Aug 31, 2025
@renovate renovate bot force-pushed the renovate/snafu-0.x-lockfile branch from 74d8882 to 44450d0 Compare August 31, 2025 09:03
@renovate renovate bot force-pushed the renovate/snafu-0.x-lockfile branch from 44450d0 to 3ec8dbd Compare September 6, 2025 23:48
@renovate renovate bot changed the title fix(deps): update rust crate snafu to v0.8.8 fix(deps): update rust crate snafu to v0.8.9 Sep 6, 2025
@renovate renovate bot changed the title fix(deps): update rust crate snafu to v0.8.9 chore(deps): update rust crate snafu to v0.8.9 Sep 25, 2025
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