Bump FluentAssertions from 6.12.0 to 6.12.1

[dependabot[bot]]

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: https://github.com/fluentassertions/fluentassertions/compare/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 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 will merge this PR once CI passes on it, as requested by @guibranco.

---

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 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)

[dependabot[bot]]

The following labels could not be found: nuget, .NET, packages, dependencies.

[korbit-ai[bot]]

By default, I don't review pull requests opened by bots. If you would like me to review this pull request anyway, you can request a review via the /korbit-review command in a comment.

[semanticdiff-com[bot]]

Review changes with SemanticDiff.

[gooroo-dev[bot]]

Please double check the following review of the pull request:

Issues counts

🐞Mistake	🤪Typo	🚨Security	🚀Performance	💪Best Practices	📖Readability	❓Others
0	0	0	0	0	0	0

Changes in the diff

• 🛠️ No changes in the code.

Identified Issues

ID	Type	Details	Severity	Confidence

Since there are no changes in the code, there are no issues to address or tests to generate.

Summon me to re-review when updated! Yours, Gooroo.dev Your feedback is important! Please react or reply.

[senior-dev-bot[bot]]

Hi there! :wave: Thanks for opening a PR. It looks like you've already reached the 5 review limit on our Basic Plan for the week. If you still want a review, feel free to upgrade your subscription in the Web App and then reopen the PR

[pr-code-reviewer[bot]]

:wave: Hi there!

Everything looks good!

_{^{Automatically generated with the help of gpt-3.5-turbo. Feedback? Please don't hesitate to drop me an email at webber@takken.io.}}

[codara-ai-code-review[bot]]

Potential issues, bugs, and flaws that can introduce unwanted behavior:

1. FluentAssertions package version was updated from 6.12.0 to 6.12.1 in the test project file. Ensure compatibility and verify that this new version doesn't introduce any breaking changes or issues in the test suite.

Code suggestions and improvements for better exception handling, logic, standardization, and consistency:

1. It's advisable to update the package versions in the test project incrementally, one version at a time, instead of jumping directly to the latest version. This helps in better tracking of potential issues if they arise.
2. Consider updating the xunit.runner.visualstudio package to a newer version if there are updates available to ensure compatibility with the other packages.

[coderabbitai[bot]]

[!IMPORTANT]

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: -- `I pushed a fix in commit , please review it.` -- `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: -- `@coderabbitai generate unit testing code for this file.` -- `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: -- `@coderabbitai generate interesting stats about this repository and render them as a table.` -- `@coderabbitai read src/utils.ts and generate unit testing code.` -- `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` -- `@coderabbitai help me debug CodeRabbit configuration file.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (Invoked using PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. ### Other keywords and placeholders - Add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. - Add `@coderabbitai summary` to generate the high-level summary at a specific location in the PR description. - Add `@coderabbitai` anywhere in the PR title to generate the title automatically. ### CodeRabbit Configuration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

[instapr[bot]]

Feedback

🚀 Updated FluentAssertions from 6.12.0 to 6.12.1.

The package reference in POCTomlHandling.Tests.csproj has been successfully updated to use version 6.12.1.

This PR looks good to merge.

[deepsource-io[bot]]

Here's the code health analysis summary for commits b7e1c0b..8295c83. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
Test coverage	✅ Success		View Check ↗
Secrets	✅ Success		View Check ↗
C#	✅ Success		View Check ↗

Code Coverage Report

Metric	Aggregate	C#
Branch Coverage	100%	100%
Composite Coverage	100%	100%
Line Coverage	100%	100%

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[github-actions[bot]]

Infisical secrets check: :white_check_mark: No secrets leaked!

Scan results:

1:31PM INF scanning for exposed secrets...
1:31PM INF 29 commits scanned.
1:31PM INF scan completed in 66.7ms
1:31PM INF no leaks found

[sonarcloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[guibranco]

@dependabot squash and merge