Skip to content
This repository was archived by the owner on Jan 13, 2026. It is now read-only.

Commit 1d779ed

Browse files
author
Jesús Miguel Benito Calzada
authored
Fix GHA release workflow (#5717)
This commit aims to fix the `Release Pipeline` of the GHA workflows (better said, to make it support testing releases, those triggered by tags following the pattern `test-vX.Y.Z`). Currently, it is failing because in the `Kubeapps General` workflow, we are setting the `running_on_tag` output variable of the `setup` job based on whether the Git ref type is `tag` and it matches the pattern `vX.Y.Z`. Given that we are controlling what tag patterns can trigger a release in the `Release Pipeline` workflow, it doesn't make sense to have this condition, as we need to make sure that it's in sync with what there is in the workflow conditions, and it's error-prone. Signed-off-by: Jesús Benito Calzada <bjesus@vmware.com>
1 parent 9798f34 commit 1d779ed

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

.github/workflows/kubeapps-general.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -134,7 +134,7 @@ jobs:
134134
echo "running_on_main=false" >> $GITHUB_OUTPUT
135135
fi
136136
137-
if [[ ${GITHUB_REF_TYPE} == "tag" && ${GITHUB_REF_NAME} =~ ^v[0-9]+ ]]; then
137+
if [[ ${GITHUB_REF_TYPE} == "tag" ]]; then
138138
echo "running_on_tag=true" >> $GITHUB_OUTPUT
139139
else
140140
echo "running_on_tag=false" >> $GITHUB_OUTPUT

0 commit comments

Comments
 (0)