fix: CDP-only netstandard2.0 build failure with System.Threading.Channels - #3512
Merged
Merged
Conversation
…dard2.0 build ScreenRecorder relies on System.Threading.Channels, which isn't part of the netstandard2.0 BCL. It compiled fine in the normal build only because the WebDriverBiDi package transitively pulled it in; the CDP-only build excludes WebDriverBiDi and failed on release. Add the package reference directly, and build the CDP-only target in CI so this is caught before a release tag, not after.
This was referenced Jul 3, 2026
This was referenced Jul 12, 2026
sondresjolyst
pushed a commit
to sondresjolyst/garge-api
that referenced
this pull request
Jul 13, 2026
Updated [PuppeteerSharp](https://github.com/hardkoded/puppeteer-sharp) from 25.2.1 to 25.3.1. <details> <summary>Release notes</summary> _Sourced from [PuppeteerSharp's releases](https://github.com/hardkoded/puppeteer-sharp/releases)._ ## 25.3.1 ## What's Changed * fix: CDP-only netstandard2.0 build failure with System.Threading.Channels by @kblok in hardkoded/puppeteer-sharp#3512 **Full Changelog**: hardkoded/puppeteer-sharp@v25.3.0...v25.3.1 ## 25.3.0 ## What's New * chore: roll Firefox to 152.0.4 (upstream #15158, #15195) by @kblok in hardkoded/puppeteer-sharp#3510 * chore: bump version to 25.3.0 by @kblok in hardkoded/puppeteer-sharp#3511 * New Feature: support installing extensions for browser contexts (#15164) by @kblok in hardkoded/puppeteer-sharp#3509 ## What's Changed * Fix: handle swaps without a timer (#15198) by @kblok in hardkoded/puppeteer-sharp#3507 * fix: don't set newWindow=true when no targets exist by @kblok in hardkoded/puppeteer-sharp#3482 * fix: normalize duplicate set-cookie headers using newline (upstream #15173) by @kblok in hardkoded/puppeteer-sharp#3508 **Full Changelog**: hardkoded/puppeteer-sharp@v25.2.1...v25.3.0 Commits viewable in [compare view](hardkoded/puppeteer-sharp@v25.2.1...v25.3.1). </details> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
This was referenced Jul 13, 2026
This was referenced Jul 20, 2026
This was referenced Jul 29, 2026
This was referenced Aug 7, 2026
This was referenced Aug 21, 2026
This was referenced Sep 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The v25.3.0 nuget publish run failed while packing the CDP-only build:
ScreenRecorder.csusesSystem.Threading.Channels, which isn't in the netstandard2.0 BCL. It only compiled in the normal build becauseWebDriverBiDi's netstandard2.0 dependency group transitively pulls inSystem.Threading.Channels— and that package reference gets excluded whenCDP_ONLYis defined, so the CDP-only netstandard2.0 target lost the package with it.Fixed by adding an explicit reference to the netstandard2.0 item group so it doesn't ride on WebDriverBiDi's coattails.
The reason CI never caught this: the CDP-only build path is only exercised by the release-tag publish workflow, never by the regular PR/push CI. Added a
build-cdp-onlyjob todotnet.ymlso this is caught before a release, not after. Also bumped the patch version to 25.3.1.Test plan
dotnet build lib/PuppeteerSharp/PuppeteerSharp.csproj /p:DefineConstants=CDP_ONLY --configuration Release --no-incrementalsucceedsdotnet build lib/PuppeteerSharp.sln --configuration Releasesucceedsdotnet format ./lib/PuppeteerSharp.sln --verify-no-changes --exclude-diagnostics CA1865clean