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

Bump FluentAssertions from 6.12.0 to 6.12.1 in /SampleProject #4

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Nov 4, 2024

Bumps FluentAssertions from 6.12.0 to 6.12.1.

Release notes

Sourced from FluentAssertions's releases.

6.12.1

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

Commits
  • a8e7f17 Update qodana
  • d58e0b5 Turn off RoslynAnalyzers in Qodana WF (#2504)
  • 2181217 Remove unused usings
  • 2c3a012 Make implicit usage more explicit
  • 1d5d64f Do not use UsingLineBreaks for [Not]BeSameAs
  • c30fc7a Fixed BeEquivalentTo when using a custom comparer targeting nullable types ...
  • f9b770b Make ThrowWithinAsync respect canceled tasks (#2614)
  • f204cf3 Simplify deferred allocation with local function
  • a3644b0 Only allocate Lazy<> and lambda when necessary
  • f3b4564 Ensured that nested assertion scopes produce a nested context (#2607)
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [FluentAssertions](https://github.com/fluentassertions/fluentassertions) from 6.12.0 to 6.12.1.
- [Release notes](https://github.com/fluentassertions/fluentassertions/releases)
- [Changelog](https://github.com/fluentassertions/fluentassertions/blob/develop/AcceptApiChanges.ps1)
- [Commits](fluentassertions/fluentassertions@6.12.0...6.12.1)

---
updated-dependencies:
- dependency-name: FluentAssertions
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the area:deps [issue/PR] adds, updates, or removes dependencies. label Nov 4, 2024
@dependabot dependabot bot requested a review from rdeago November 4, 2024 17:52
Copy link
Contributor Author

dependabot bot commented on behalf of github Nov 8, 2024

Superseded by #8.

@dependabot dependabot bot closed this Nov 8, 2024
@dependabot dependabot bot deleted the dependabot/nuget/SampleProject/FluentAssertions-6.12.1 branch November 8, 2024 17:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:deps [issue/PR] adds, updates, or removes dependencies.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants