Skip to content

chore(deps): update rust crate pretty_assertions to v1 #12

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

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

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Oct 18, 2021

This PR contains the following updates:

Package Type Update Change
pretty_assertions dev-dependencies major 0.6.1 -> 1.0.0

Release Notes

rust-pretty-assertions/rust-pretty-assertions (pretty_assertions)

v1.4.1

Compare Source

Fixed

Internal

v1.4.0

Compare Source

Changed

  • (Windows only) Removed the ctor and output_vt100 dependencies, as their benefit could not be demonstrated (#​118)

Fixed

  • Minor documentation fixes (#​107)

v1.3.0

Compare Source

Changed

  • MSRV bumped to 1.54.0 (see #​102)
  • Removed the publically re-exported ansi_term::Style. This was never intended for public use. (see #​102)

Fixed

  • Moved from the unmaintained ansi_term crate to yansi for ANSI terminal escape code support. Thanks to @​Roguelazer for reporting and fixing this! (#​102, @​Roguelazer)

v1.2.1

Compare Source

Fixed

v1.2.0

Compare Source

Changed

v1.1.0

Compare Source

Added

  • Add assert_str_eq for comparing two str-like values without Debug formatting. Thanks to @​x3ro for implementing this! (#​88, @​x3ro)

Fixed

v1.0.0

Compare Source

Removed

  • assert_ne no longer warns if values match using PartialEq but not with Debug. This was noted as no longer being necessary after Rust 1.25 (current MSRV 1.35.0)

Added

  • Officially support no_std (thanks to @​Luro02 for the report and reviews!). Adds the std and alloc features to the pretty_assertions crate, with std enabled by default (#​83, @​tommilligan)
  • Adds the unstable feature to the pretty_assertions crate, for use with nightly rustc (#​81, @​tommilligan)
  • Add a drop in replacement for the unstable stdlib assert_matches macro, behind the unstable flag - thanks @​gilescope for the suggestion! (#​81, @​tommilligan)

v0.7.2

Compare Source

v0.7.1

Compare Source

v0.7.0

Compare Source

Changed

  • Move from difference to diff for calculating diffs. The exact assertion messages generated may differ from previous versions. (#​52, @​tommilligan)

For example, the following assertion message from v0.7.0:

pretty assertion

Was previously rendered like this in v0.6.1:

pretty assertion

Added

Fixed

Internal


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/pretty_assertions-1.x branch from 9bf8a9e to b8b7744 Compare March 7, 2022 13:52
@renovate renovate bot force-pushed the renovate/pretty_assertions-1.x branch from b8b7744 to 2834c9e Compare March 26, 2022 14:31
@renovate renovate bot force-pushed the renovate/pretty_assertions-1.x branch from 2834c9e to 8852078 Compare April 24, 2022 21:18
@renovate renovate bot force-pushed the renovate/pretty_assertions-1.x branch from 8852078 to ff80b6c Compare September 25, 2022 22:01
@renovate renovate bot force-pushed the renovate/pretty_assertions-1.x branch from ff80b6c to 688885e Compare November 20, 2022 16:43
@renovate renovate bot force-pushed the renovate/pretty_assertions-1.x branch from 688885e to bf7971d Compare July 6, 2023 18:58
@renovate renovate bot force-pushed the renovate/pretty_assertions-1.x branch from bf7971d to 6d8817b Compare May 5, 2024 09:40
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants