Skip to content

Update dependency FluentAssertions to 6.12.2#271

Merged
RLittlesII merged 1 commit intomasterfrom
renovate/fluentassertions-6.x
Feb 21, 2025
Merged

Update dependency FluentAssertions to 6.12.2#271
RLittlesII merged 1 commit intomasterfrom
renovate/fluentassertions-6.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Feb 1, 2025

This PR contains the following updates:

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

Release Notes

fluentassertions/fluentassertions (FluentAssertions)

v6.12.2

Compare Source

What's Changed
Others

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

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 - "after 3am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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 added the 📦 dependencies Pull requests that update a dependency file label Feb 1, 2025
@github-actions github-actions bot added this to the v0.11.2 milestone Feb 1, 2025
@RLittlesII RLittlesII merged commit 6f15a98 into master Feb 21, 2025
@RLittlesII RLittlesII deleted the renovate/fluentassertions-6.x branch February 21, 2025 23:35
@rsg-bot rsg-bot modified the milestones: v0.11.2, v0.12.0 Dec 4, 2025
@github-actions github-actions bot modified the milestones: v0.12.0, v0.12.1 Dec 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

📦 dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants