stakater / Reloader

A Kubernetes controller to watch changes in ConfigMap and Secrets and do rolling upgrades on Pods with their associated Deployment, StatefulSet, DaemonSet and DeploymentConfig – [✩Star] if you're using it!

Home Page:https://docs.stakater.com/reloader/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

[BUG] Recent CI authored auto-releases are broken!

kakkoyun opened this issue · comments

Describe the bug
0838acd

Screenshot 2024-04-26 at 19 27 19

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!

Screenshot 2024-04-26 at 19 27 37

version: 1.0.85
appVersion: v1.0.85

to

version: v1.0.86
appVersion: vv1.0.86

must have been that version started getting v prefix

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: