Fix patch installer workflow failure by providing default values for push events

[Copilot]

The Patch Installer workflow (patch-installer-cd.yml) was failing during push events because the "Upload Patch to S3" step was receiving empty values for BASE_RELEASE and BASE_BUILD_NUMBER environment variables.

Problem

GitHub Actions inputs are only available during workflow_dispatch events. When the workflow is triggered by push events, expressions like ${{ inputs.base_release }} evaluate to empty strings rather than their defined default values, causing this error:

Must have a base_build_number nor a valid base_release to support automatic updating

Solution

Modified the environment variable declarations to use GitHub Actions' fallback syntax:

env:
  BASE_RELEASE: ${{ inputs.base_release || 'build-1141' }}
  BASE_BUILD_NUMBER: ${{ inputs.base_build_number || '' }}

This ensures that:

• During workflow_dispatch events: Uses the provided input values
• During push events: Uses the default value 'build-1141' for BASE_RELEASE

Impact

The workflow now works correctly for both manual triggers and automatic push events. Patch installers will be properly uploaded to S3 with the correct naming pattern expected by the FwUpdater.cs automatic update system:

jobs/FieldWorks-Win-all-Release-Patch/[build-number]/FieldWorks_[version]_b[base-build]_x64.msp

This is a minimal, surgical fix that changes only 2 lines to resolve the workflow failure while maintaining backward compatibility with manual workflow dispatches.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

---

This change is 

[jasonleenaylor]

@jasonleenaylor reviewed 1 of 1 files at r2, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @copilot)

[jasonleenaylor]

@jasonleenaylor reviewed all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @copilot)