Conversation
|
/cherry-pick release-0.4 In case that this is the fix. |
|
@ntnn: once the present PR merges, I will cherry-pick it on top of DetailsIn response to this:
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-sigs/prow repository. |
Signed-off-by: Nelo-T. Wallus <red.brush9525@fastmail.com> Signed-off-by: Nelo-T. Wallus <n.wallus@sap.com>
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: xrstf The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
LGTM label has been added. DetailsGit tree hash: 6ef0753ad8588928054628d0a3a5cd6b0c22e732 |
|
@ntnn: new pull request created: #153 DetailsIn response to this:
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-sigs/prow repository. |
Summary
Possible fix for #151
I think the
| greponly applies to theecho v0.0.0before it and not the plumbing commands.So
git describe ...was always getting the tag but with the whitespace around it and thegrep -odidn't apply and that's why the comparison withVERSIONalways failed and the latest tag was never updated.What Type of PR Is This?
/kind bug
Related Issue(s)
Fixes #
Release Notes