Fix step success reporting on Gradle failure #69
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes an issue where GitHub Actions steps in the
update-scheduled-release-version.yml
workflow would incorrectly report success even if an internal Gradle task failed.The problem was caused by wrapping the Gradle execution directly within an
echo "key=$(./gradlew ...)" >> $GITHUB_OUTPUT
command. Theecho
command itself would succeed, masking the underlying Gradle failure.This change modifies the script to:
$GITHUB_OUTPUT
using thekey=value
format.This ensures that if the Gradle task fails, the step will now correctly report a failure.
Addresses #15
Related to spring-projects/spring-security#16764