From 3db996dd0fe2721bf86041fc00762625be1efbfa Mon Sep 17 00:00:00 2001 From: jcant0n Date: Sun, 2 Aug 2026 15:49:50 +0200 Subject: [PATCH] feat: expose force-publish on manual CD runs Wires the toolbox v1.4.0 input through so a person can ship a regeneration an agent already produced and a reviewer already merged. Without it that work never reaches nuget.org: the pull request commits the regenerated output, so when CD next runs it regenerates identical bytes, finds nothing changed, and skips publishing. The scheduled path is untouched -- the gate still stops Khronos typos from producing version bumps that mean nothing. --- .github/workflows/CD.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/.github/workflows/CD.yml b/.github/workflows/CD.yml index 5570149..696e62f 100644 --- a/.github/workflows/CD.yml +++ b/.github/workflows/CD.yml @@ -13,6 +13,11 @@ on: required: false type: boolean default: false + force-publish: + description: 'Publish even if the generated API did not change (for shipping a reviewed regeneration)' + required: false + type: boolean + default: false schedule: - cron: '30 1 1 * *' # Monthly update on day 1 at 01:30 @@ -32,6 +37,7 @@ jobs: runtime-identifier: "" # Runtime identifier (win-x64, linux-x64, etc.) build-configuration: "Release" # Build configuration (Release, Debug, etc.) revision: ${{ github.run_number }} # Revision for date-based version (bindings style). Use with bindings. + force-publish: ${{ inputs.force-publish || false }} publish-enabled: ${{ !inputs.skip-assets-publishing }} enable-email-notifications: true secrets: