-
Notifications
You must be signed in to change notification settings - Fork 512
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Recent CI authored auto-releases are broken! #649
Comments
to
must have been that version started getting |
docs images are pushed with https://github.com/stakater/.github/blob/main/.github/workflows/push_container.yaml which add v by default |
we push all images with "v" but when pushing the chart we remove the "v" from the version 🙄 |
In https://github.com/stakater/Reloader/actions/runs/8851628050/job/24308595322 it is not getting any new commits for some reason so it is not generating the operator tag properly |
Rerunning the job to see if it is some flaky behavior of github-tag-action |
So on rerun the action correctly generated a new tag: Bumping tag v1.0.87 - New tag 1.0.88 however then it failed with another push issue so rerunning again |
The later failure could be related to #636 |
The last bump 9a9fee2 went as expected so I will troubleshoot a little more to see under what circumstances we get the v prefix |
Thanks for looking into this ❤️ |
Yes it's something with the doc workflow that is causing the v prefix to appear d4b7d38 |
This should be resolved now, it was most probably a race condition where two push workflows ran at the same time:
|
Describe the bug
0838acd
CI introduces an additional
v
as a prefix.To Reproduce
helm upgrade
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
Failure!
The text was updated successfully, but these errors were encountered: