Closed noah-prosperops closed 11 months ago
I am also now seeing this issue and it is a major blocking problem as our org defines which versions of actions are allowed and this had been defined as v1 and not v1.4.1 which would have prevented this breaking version (1.5.0) from automatically being used. Can this be fixed ASAP or in the interim publish a revert until the cause is determined so that it will unblock workflows that target v1 as the version?
Cc @scefali for visibility
Yea, let me revert.
Yea, let me revert.
Thank you!
@scefali it looks like the revert alone didn't fix the issue because targeting v1 tries to pull latest from ghcr and I assume that is still pointing at the 1.5.0 release?
Yea it looks like this https://github.com/getsentry/action-release/pkgs/container/action-release-image/155367620?tag=latest is still what gets pulled
We're also still experiencing the same issue at the moment 🙏
Damn, I guess deleting the release in GH and setting 1.4.1 the latest didn't work. Hopefully rolling forward with a new version works: https://github.com/getsentry/action-release/releases/tag/v1.6.0
That fixed it, thank you very much for the quick fix!
Confirmed working from our end as well. Thanks!
Ok closing again
Github Sentry Action Release Bug Report
Environment
We're seeing this occur in our self-hosted runner shortly after the latest release.
How do you use this action?
Self-hosted runner on Ubuntu 22.04
Which version of the action?
v1
Steps to Reproduce
Run workflow, observe error while executing
getsentry/action-release@v1
Expected Result
No error. This worked an hour ago.
Actual Result
See error above