Skip to content

Commit 5cf53b0

Browse files
Let standalone public-operator dispatch publish a pre-release
publish-public-operator-docker-image.yaml hard-coded force_release:'no', so a manual (workflow_dispatch) build on main produced a deployable image with no tag and no GitHub Release — which the uid2-deployment release gate (UID2-6767) would then hard-block on deploy. Add a force_release input: 'branch' default on workflow_dispatch (releases only Patch/Minor/Major builds on the default/release branch — feature-branch and Snapshot dispatches still create nothing), and 'no' default on workflow_call. Pass it through to the shared build. publish-all-operators passes 'no' explicitly so only its createRelease job cuts the single combined Release — no double-up. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
1 parent 69b2622 commit 5cf53b0

2 files changed

Lines changed: 14 additions & 1 deletion

File tree

.github/workflows/publish-all-operators.yaml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -106,6 +106,7 @@ jobs:
106106
release_type: ${{ needs.start.outputs.release_type }}
107107
version_number_input: ${{ needs.start.outputs.new_version }}
108108
vulnerability_severity: ${{ needs.start.outputs.vulnerability_severity }}
109+
force_release: 'no' # The createRelease job below publishes the single combined Release; the component build must not.
109110
secrets: inherit
110111

111112
buildGCP:

.github/workflows/publish-public-operator-docker-image.yaml

Lines changed: 13 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,14 @@ on:
2222
- CRITICAL,HIGH
2323
- CRITICAL,HIGH,MEDIUM
2424
- CRITICAL (DO NOT use if JIRA ticket not raised)
25+
force_release:
26+
description: "Create a GitHub Release for this build. 'branch' (default) releases only Patch/Minor/Major builds on the default or a release branch; 'no' skips; 'yes' forces a release regardless of branch."
27+
type: choice
28+
default: branch
29+
options:
30+
- branch
31+
- "no"
32+
- "yes"
2533

2634
workflow_call:
2735
inputs:
@@ -37,6 +45,10 @@ on:
3745
description: The severity to fail the workflow if such vulnerability is detected. DO NOT override it unless a Jira ticket is raised. Must be one of ['CRITICAL', 'CRITICAL,HIGH' or 'CRITICAL,HIGH,MEDIUM'] (without space in between).
3846
type: string
3947
default: 'CRITICAL,HIGH'
48+
force_release:
49+
description: Whether the shared build should publish a GitHub Release. The parent publish-all-operators passes 'no' because it creates the combined Release itself.
50+
type: string
51+
default: 'no'
4052

4153
outputs:
4254
image_tag:
@@ -66,7 +78,7 @@ jobs:
6678
with:
6779
release_type: ${{ inputs.release_type }}
6880
version_number_input: ${{ inputs.version_number_input }}
69-
force_release: 'no' # Do not create a release for the component builds, will be created by the parent
81+
force_release: ${{ inputs.force_release }} # Standalone dispatch: 'branch' default releases main builds. From publish-all-operators: 'no' (parent creates the combined Release).
7082
vulnerability_severity: ${{ inputs.vulnerability_severity }}
7183
java_version: 21
7284
merge_environment: ${{ github.ref_protected && 'ci-auto-merge' || '' }}

0 commit comments

Comments
 (0)