W-21616134: trigger CBW release after publishing extensions to marketplace (#7011)

* feat: trigger CBW release after publishing extensions to marketplace

Add trigger-cbw-release job to publishVSCode.yml that fires a
repository_dispatch event to forcedotcom/code-builder-web after extensions
are successfully published. Fire-and-forget — does not block CTC close.

* fix: make CBW dispatch non-blocking so publish failures don't fail the workflow

* feat: add CBW_TRIGGER_ENABLED to toggle promote-on-publish dispatch

- Add repo variable check (default enabled, set false to disable)
- Document in contributing/publishing.md

Author: jonnyhork

.github/workflows/publishVSCode.yml

@@ -83,3 +83,24 @@ jobs:
     with:
       changeCaseId: ${{ needs.ctc-open.outputs.changeCaseId }}
       status: Not Implemented
+
+  # Set repo variable CBW_TRIGGER_ENABLED=false to disable dispatch to code-builder-web.
+  # Default (unset): dispatch after publish. Use when publishing without CBW promotion.
+  trigger-cbw-release:
+    needs: [publish, prepare-environment-from-main]
+    if: needs.publish.result == 'success' && vars.CBW_TRIGGER_ENABLED != 'false'
+    continue-on-error: true
+    runs-on: ubuntu-latest
+    steps:
+      - name: Trigger Code Builder Web release
+        env:
+          GH_TOKEN: ${{ secrets.IDEE_GH_TOKEN }}
+        run: |
+          VERSION="${{ needs.prepare-environment-from-main.outputs.RELEASE_VERSION }}"
+          echo "Dispatching extension-publish event to code-builder-web with version $VERSION"
+          gh api repos/forcedotcom/code-builder-web/dispatches \
+            --method POST \
+            -f event_type=extension-publish \
+            -f "client_payload[version]=$VERSION" \
+            -f "client_payload[source]=publishVSCode"
+          echo "Dispatch sent successfully"

contributing/publishing.md

@@ -80,6 +80,8 @@ find ~/Downloads/v64.8.0 -type f -name "*.vsix" -exec code --install-extension {
 
 After completing your release testing following our internal template, approve the publish job "Publish in Microsoft Marketplace" and "Publish in Open VSX Registry" to allow the extensions to be uploaded and complete the release process.
 
+**Code Builder Web promotion:** After publishing to the MS Marketplace, the workflow dispatches to `code-builder-web` to trigger a CBW release and auto-promote to production. Set repo variable `CBW_TRIGGER_ENABLED=false` (Settings → Secrets and variables → Actions → Variables) to publish without triggering CBW. Default (unset) enables the trigger.
+
 ## Troubleshooting
 
 - 401 errors on publish? You probably need to update the VSCE PAT. https://salesforce.quip.com/E8GWA5TuI8jp