We were upgrading from v3 to v4 when we noticed this happening. We were aware that the output for this action had changed and we were incorrectly using releases_created but the issue was that we were gating production deployments off of this flag. So the fact that it defaulted to true unexpectedly was the issue we observed.
Worth noting when we switch to release_created this flag was working as expected.
I recreated our deployments in this repo if you wanna check out our deploy workflow.
TL;DR
We noticed when upgrading from v3 to v4 that the
releases_created
output is defaulting to true even when no release was created.Expected behavior
I would expect
releases_created
to be set tofalse
if no release was created.Observed behavior
releases_created
was set totrue
when no release was created.Action YAML
Log output
Additional information
We were upgrading from v3 to v4 when we noticed this happening. We were aware that the output for this action had changed and we were incorrectly using
releases_created
but the issue was that we were gating production deployments off of this flag. So the fact that it defaulted to true unexpectedly was the issue we observed.Worth noting when we switch to
release_created
this flag was working as expected.I recreated our deployments in this repo if you wanna check out our deploy workflow.