deps(dotnet): Bump CefSharp.Wpf.NETCore from 148.0.90 to 149.0.60

[dependabot]

Updated CefSharp.Wpf.NETCore from 148.0.90 to 149.0.60.

Release notes

Sourced from CefSharp.Wpf.NETCore's releases.

No release notes found for this version range.

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

[github-actions]

AI Analysis

Technical Summary:

This pull request updates the NuGet package dependency for CefSharp.Wpf.NETCore from version 148.0.90 to 149.0.60.

Technical Requirements and Constraints:

• The upgrade requires compatibility with the newer version of CefSharp.Wpf.NETCore, which is a .NET Core wrapper for the Chromium Embedded Framework (CEF) targeting WPF applications.
• Ensure that the project’s .NET Core version and other dependencies remain compatible with CefSharp 149.0.60.
• There may be native or platform-specific binaries involved, so platform runtime compatibility should be verified.

Implementation Considerations:

• The update is a straightforward version bump without manual code changes described in the PR.
• Testing the application thoroughly after upgrade is necessary to ensure no unexpected behavior, especially given that no release notes or specific changelog details were available for the version range.
• Verify references and binding redirects if applicable to avoid runtime assembly conflicts.

---

This summary was automatically generated by AI to help with triage and may not be 100% accurate.

[dependabot]

Superseded by #111.