Automation

[DJGosnell]

Automates the PDFium bindings update pipeline that was previously a manual process (run generator locally, commit, tag, push). Introduces a bi-weekly GitHub Action that detects new https://github.com/bblanchon/pdfium-binaries releases, generates C# bindings, and publishes to NuGet — fully hands-off.

What changed

New: .github/workflows/check-update.yml

• Bi-weekly cron (1st and 15th of each month) + manual workflow_dispatch
• Detects new upstream releases via GitHub API, compares against Directory.Build.props
• Supports targeting a specific version via dispatch input (e.g. 134.0.6996.0)
• Verifies bblanchon.PDFium.Win32 NuGet package exists before proceeding
• Generates bindings, builds, tests, then commits + tags directly to master
• Tag push triggers existing publish pipeline in dotnet.yml

Modified: .github/workflows/dotnet.yml

• Bumped actions/checkout to v4, softprops/action-gh-release to v2
• Replaced olegtarasov/get-tag action with inline GITHUB_REF parsing
• Replaced download_package.sh with direct generator call using latest true so PR/branch builds always resolve the latest upstream version
• Limited push trigger to master only to prevent double-triggering on PRs

Modified: src/PDFiumCoreBindingsGenerator/PDFiumCoreLibrary.cs

• Gated SetupMSVC() behind RuntimeInformation.IsOSPlatform(OSPlatform.Windows) so CppSharp runs on Ubuntu runners using its bundled clang headers

Pipeline flow

Cron/Dispatch → Detect new version → Verify NuGet exists → Generate bindings
→ Build + Test → Commit to master → Tag → dotnet.yml publishes to NuGet

Test plan

• Trigger check-update.yml via workflow_dispatch with force_update: true to validate full pipeline
• Verify CppSharp generates identical bindings on Ubuntu vs Windows (diff should only show timestamp)
• Confirm dotnet.yml triggers exactly once on PR (no double runs)
• End-to-end: verify tag push produces a GitHub release and NuGet package