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.

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

chore(deps): update dependency fluentassertions to 6.12.1 #344

Merged
merged 1 commit into from
Sep 21, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 19, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
FluentAssertions (source) 6.12.0 -> 6.12.1 age adoption passing confidence

Release Notes

fluentassertions/fluentassertions (FluentAssertions)

v6.12.1

Compare Source

What's Changed
Improvements
  • Improve BeEmpty() and BeNullOrEmpty() performance for IEnumerable<T>, by materializing only the first item - #​2530
Fixes
  • Fixed formatting error when checking nullable DateTimeOffset with BeWithin(...).Before(...) - #​2312
  • BeEquivalentTo will now find and can map subject properties that are implemented through an explicitly-implemented interface - #​2152
  • Fixed that the because and becauseArgs were not passed down the equivalency tree - #​2318
  • BeEquivalentTo can again compare a non-generic IDictionary with a generic one - #​2358
  • Fixed that the FormattingOptions were not respected in inner AssertionScope - #​2329
  • Capitalize true and false in failure messages and make them formattable to a custom BooleanFormatter - #​2390, #​2393
  • Improved the failure message for NotBeOfType when wrapped in an AssertionScope and the subject is null - #​2399
  • Improved the failure message for BeWritable/BeReadable when wrapped in an AssertionScope and the subject is read-only/write-only - #​2399
  • Improved the failure message for ThrowExactly[Async] when wrapped in an AssertionScope and no exception is thrown - #​2398
  • Improved the failure message for [Not]HaveExplicitProperty when wrapped in an AssertionScope and not implementing the interface - #​2403
  • Improved the failure message for [Not]HaveExplicitMethod when wrapped in an AssertionScope and not implementing the interface - #​2403
  • Changed BeEquivalentTo to exclude private protected members from the comparison - #​2417
  • Fixed using BeEquivalentTo on an empty ArraySegment - #​2445, #​2511
  • BeEquivalentTo with a custom comparer can now handle null values - #​2489
  • Ensured that nested calls to AssertionScope(context) create a chained context - #​2607
  • One overload of the AssertionScope constructor would not create an actual scope associated with the thread - #​2607
  • Fixed ThrowWithinAsync not respecting OperationCanceledException - #​2614
  • Fixed using BeEquivalentTo with an IEqualityComparer targeting nullable types - #​2648

Full Changelog: fluentassertions/fluentassertions@6.12.0...6.12.1


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.

@ChrisPulman ChrisPulman merged commit 073c52c into main Sep 21, 2024
2 checks passed
@ChrisPulman ChrisPulman deleted the renovate/fluentassertions-6.x branch September 21, 2024 12:24
Copy link

github-actions bot commented Oct 6, 2024

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 6, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant