Helm OCI artifact gets updated after initial release

[chrede88]

Checks

• I've already read https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/troubleshooting-actions-runner-controller-errors and I'm sure my issue is not covered in the troubleshooting guide.
• I am using charts that are officially provided

Controller Version

0.12.0

Deployment Method

Helm

Checks

• This isn't a question or user support case (For Q&A and community support, go to Discussions).
• I've read the Changelog before submitting this issue and I'm sure it's not due to any recently-introduced backward-incompatible changes

To Reproduce

1. Install using OCI artifact
2. OCI artifact gets updated (new digest)
3. CD controllers roll out new containers

Describe the bug

The Helm OCI artifact (for the action runner controller) gets updated after inital release. This is not good, as releases shouldn't get updated after the inital release. I don't think the release actually gets updated with new code, it just gets overwritten (but I could be wrong). In any case, as the digest is updated, CD tools (like Flux) will pull the new artifact and roll out new containers.

In time of writing (5:35pm UTC, June 16th) the 0.12.0 release was updated ~1h ago: https://github.com/actions/actions-runner-controller/pkgs/container/actions-runner-controller-charts%2Fgha-runner-scale-set-controller/439315276?tag=0.12.0

Describe the expected behavior

Releases doesn't get updated after inital release.

Additional Context

N/A

Controller Logs

N/A

Runner Pod Logs

N/A

[github-actions]

Hello! Thank you for filing an issue.

The maintainers will triage your issue shortly.

In the meantime, please take a look at the troubleshooting guide for bug reports.

If this is a feature request, please review our contribution guidelines.

[AngellusMortis]

This also causes issues with some tools as well as they pulled the original 0.12.0 release and will not accept the overwritten version (at least not without a lot of hacks that should not be done).

We probably need a new 0.12.1 chart release.

[ilbarone87]

Caused by this #4125 (comment)

[chrede88]

Caused by this #4125 (comment)

Not great that this was done on purpose. Hopefully it won't happen in the future. Should have been a new patch release.

[tyriis]

This is an anti pattern, a release is a release. Just roll out a fix with the last number and nobody is unhappy, like this you create a lot of issues in automated and secured environments.

[nikola-jokic]

We can close this one now. We will try to avoid doing it in the future...