build: avoid unnecessary steps in release-please workflow #10
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.
Fixes #8
In GitHub actions, steps' output properties always have string values.
Per https://github.com/google-github-actions/release-please-action/issues/912 and https://github.com/google-github-actions/release-please-action/pull/915, a breaking change in
release-please-action@v4
is that when there are no releases created, instead of omittingreleases_created
property it sets it to a truthy string"false"
.This PR updates the condition
if: ${{ steps.release.outputs.releases_created }}
toif: ${{ steps.release.outputs.releases_created == 'true' }}
to avoid running unnecessary steps when there are no releases created.