Skip to content

Commit

Permalink
Use correct tag in comment / use correct branch for release action
Browse files Browse the repository at this point in the history
Signed-off-by: Sascha Schwarze <schwarzs@de.ibm.com>
  • Loading branch information
SaschaSchwarze0 committed Jan 9, 2025
1 parent 716e951 commit 2727d56
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion .github/report-release-vulnerabilities.sh
Original file line number Diff line number Diff line change
Expand Up @@ -148,10 +148,11 @@ if [ "${hasVulnerabilities}" == "true" ] && [ "${allVulnerabilitiesFixedByRebuil
else
echo "[INFO] Triggering build of release ${nextTag} for branch ${RELEASE_BRANCH}"
gh workflow run release.yaml \
--ref "${RELEASE_BRANCH}" \
--raw-field "git-ref=${RELEASE_BRANCH}" \
--raw-field "tags=${RELEASE_TAG}" \
--raw-field "release=${nextTag}"

gh issue comment "${issueNumber}" --body "Triggered a release build in branch ${RELEASE_BRANCH} for ${RELEASE_TAG}. Please check whether this succeeded. A maintainer must release this."
gh issue comment "${issueNumber}" --body "Triggered a release build in branch ${RELEASE_BRANCH} for ${nextTag}. Please check whether this succeeded. A maintainer must release this."
fi
fi

0 comments on commit 2727d56

Please sign in to comment.