release: use correct exit code

[zegl]

This bug was found with shellcheck.

This updates #528

[k8s-ci-robot]

Hi @zegl. Thanks for your PR.

I'm waiting for a kubernetes-sigs or kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[aojea]

@BenTheElder I think that you are the expert here :)

[BenTheElder]

technically 255 would be the equivalent code on many platforms (the spec only mentions 8 bits and signed -> unsigned -1 -> 255), but in this case we're just setting any non-zero exit code so 1 SGTM :-)

[aojea]

/assign @BenTheElder

[aojea]

/lgtm

[aojea]

/ok-to-test

[BenTheElder]

thanks!

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BenTheElder, zegl

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [BenTheElder]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment