Cef.sdk nuget release schedule/process

[m-kovac]

I just wanted to ask what is the release schedule/process for the https://www.nuget.org/packages/cef.sdk package. We would like to create CefSharp v144 release with newest Cef binary v144.0.30. But the latest version of the nuget package at this moment is v144.0.27. Is there any way we could get the latest cef.sdk package version published? Thanks!

[jozefizso]

The Chromium 144.0.7559.257 LTS release from July 8, 2026 was built as Chromium Embedded Framework (CEF) 144.0.30+g9e70dde+chromium-144.0.7559.257.

@m-kovac - We we need cef-binary release v144.0.30 (not the v140.0.30 as reported). And the latest release is 144.0.27

https://chromereleases.googleblog.com/2026/07/long-term-support-channel-update-for.html

https://cef-builds.spotifycdn.com/index.html#windows64:144.0.30

[amaitland]

I have tagged a new build. Though it had me thinking.

Do you actually need a new CefSharp release? Given that there aren't any CefSharp specific changes, you should be able to replace the CEF runtime files (you could even do this at runtime). The wrapper should load the newer version without issues.

CEF introduced API compatibility a while back, given you are using builds from the same branch it should just work.

[jozefizso]

The CefSharp.WinForms has exact version dependency on the CefSharp.Common which also has exact dependency on the cef-binary packages:

CefSharp.WinForms 144.0.270
  CefSharp.Common (= 144.0.270)
    chromiumembeddedframework.runtime.win-x64 (= 144.0.27)
    chromiumembeddedframework.runtime.win-x86 (= 144.0.27)

I don't think we can override dependency version in NuGet if exact version matches are defined.

Perhaps dependencies in NuGet can be defined so the runtime packages would always be resolved to the latest available release for given major/minor track.

Publishing main CefSharp for the v144.0.30 release would make it more discoverable for customers to know the release exists and they must update.

[m-kovac]

Oh.. yes, thanks for pointing it out, I've updated the original question.