Bump YamlDotNet from 16.1.0 to 16.1.2

[dependabot]

Bumps YamlDotNet from 16.1.0 to 16.1.2.

Release notes

Sourced from YamlDotNet's releases.

Release 16.1.2

What's Changed

• Fix warnings when building in linux due to IDE0055 bugs by @​EdwardCooke in aaubry/YamlDotNet#978

Full Changelog: aaubry/YamlDotNet@v16.1.1...v16.1.2

Release 16.1.1

What's Changed

• Enable .NET analyzers by @​lahma in aaubry/YamlDotNet#928
• Dont use enummember attribute when it's null or empty by @​EdwardCooke in aaubry/YamlDotNet#967
• Eliminate allocs in TypeConverterCache lookup path by @​MattKotsenas in aaubry/YamlDotNet#969
• Fix build warnings in linux by @​EdwardCooke in aaubry/YamlDotNet#970
• Prevent forced quoting of strings with leading backslash by @​jcbfaulks in aaubry/YamlDotNet#972
• Switch from .nuspec files to project properties by @​MattKotsenas in aaubry/YamlDotNet#958
• Fix analyzer warnings on NET 9 SDK by @​lahma in aaubry/YamlDotNet#971
• Convert to use Central Package Management by @​lahma in aaubry/YamlDotNet#973
• Warnings as errors and compiler error cleanup by @​EdwardCooke in aaubry/YamlDotNet#976

New Contributors

• @​jcbfaulks made their first contribution in aaubry/YamlDotNet#972

Full Changelog: aaubry/YamlDotNet@v16.1.0...v16.1.1

Commits

• 485daaa Merge pull request #978 from EdwardCooke/ec-fixlinuxwarnings
• 86c870d Fix warnings when building in linux due to IDE0055 bugs
• 006090b Merge pull request #976 from EdwardCooke/ec-warningsaserrors
• a39e88a Use build.props and fix all warnings
• f323881 Merge pull request #973 from lahma/cpm
• cc914f3 Convert to use Central Package Management
• 3d2e577 Merge pull request #971 from lahma/analyzer-fixes
• 00026fb Merge pull request #958 from MattKotsenas/refactor/dotnet-pack
• 1127009 Merge pull request #972 from jcbfaulks/no_quote_backslash
• 42f684d test for both single and double quotes
• 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 it's up-to-date and 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 <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)

[dependabot]

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

[korbit-ai]

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.

[senior-dev-bot]

Hi there! 👋 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

[semanticdiff-com]

Review changes with SemanticDiff.

[pr-code-reviewer]

👋 Hi there!

1. Update the YamlDotNet package version from 16.1.0 to 16.1.2.
2. Ensure consistency in package versions by potentially updating SharpYaml as well.
3. Review the necessity of these specific package versions for compatibility and functionality.

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

[gooroo-dev]

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 detected in the diff.

Identified Issues

ID	Type	Details	Severity	Confidence

Since the diff is empty, there are no issues to report.

Missing Tests

No changes were detected in the diff, so no new tests are required.

Summon me to re-review when updated! Yours, Gooroo.dev
Feel free to react or reply with your thoughts!

[codara-ai-code-review]

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

1. POCYamlHandling.csproj:
   • Updating the YamlDotNet package version to 16.1.2 may introduce breaking changes or compatibility issues with the existing codebase or dependencies. It's crucial to verify that this new version is compatible with all parts of the project.

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

1. POCYamlHandling.csproj:
   • Consider checking release notes or documentation for YamlDotNet version 16.1.2 to understand any breaking changes or new features that might affect the current code.
   • Before upgrading the package version, it's a good practice to create a separate branch, update the package, and run comprehensive tests to ensure that the new version works as expected with the project's current setup.
   • Document the reason behind the package upgrade in the project documentation or version control system for future reference.

[instapr]

Feedback

• Updated YamlDotNet from 16.1.0 to 16.1.2.
• Dependency type: direct:production
• Update type: version-update:semver-patch

The changes look good! Thank you for updating the YamlDotNet dependency.

[deepsource-io]

Here's the code health analysis summary for commits a8d1a61..8ee7879. 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	60%	60%
Line Coverage	60%	60%

---

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

[coderabbitai]

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:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  -- I pushed a fix in commit <commit_id>, 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 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 for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[guibranco]

Automatically approved by gstraccini[bot]

[guibranco]

@dependabot squash and merge

[github-actions]

Infisical secrets check: ✅ No secrets leaked!

Scan results:

4:12AM INF scanning for exposed secrets...
4:12AM INF 30 commits scanned.
4:12AM INF scan completed in 65.1ms
4:12AM INF no leaks found

[sonarcloud]

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