https://cloudposse.com logo
Join Slack
Powered by
Hey folks. Something is off, it's probably a timin...
# atmos-dev
j
Hey folks. Something is off, it's probably a timing issue somewhere in the release pipelines: ā€¢ The tagged 1.233.0 release points to the git tag 
v1.233.0
which points to 
12f83b5
. ā€¢ The release assets added to that release, point to 
b392e54f7
, which is 3 commits before 
12f83b5
. One-liner to check the sha on the release binary:
Copy code
d=$(mktemp -d) && gh release download v1.233.0 -R cloudposse/atmos -p atmos_1.233.0_darwin_arm64 -D "$d" && go version -m "$d/atmos_1.233.0_darwin_arm64" | grep vcs.revision; rm -rf "$d"

	build	vcs.revision=b392e54f74a9c436d2c27fc8ba1b82605e95b58e
whereas:
Copy code
git ls-remote <https://github.com/cloudposse/atmos> refs/tags/v1.233.0
12f83b5248253662d8af06030e3966034a7ef5d4	refs/tags/v1.233.0
Fwiw, poked my stick into this because I was removing my work-around for the git credential injection issue that was fixed with 
12f83b5
, but unfortunately is not present in the latest release assets šŸ˜…
e
That is very odd!
@Igor Rodionov are you around to take a look?
i
yea
j
I suspect some actions running together and some taking longer than others, perhaps, and then last action winning and overwriting the assets. Just a guess.
Let me know if I can be of help here, also around šŸ™‚
Any new insights here? šŸ˜‡ Think the cleanest way forward might be to just cut a patch release with the 3 fix commits? šŸ¤”
e
@Andriy Knysh (Cloud Posse) can you do that; make sure we don't merge any PRs until after the CI completes. @Igor Rodionov is looking into the proper fix, but we understand what happened.
šŸ™ 1
šŸ‘€ 1
alert Unfortunately our release process is broken right now. We tried to cut 1.231.1, but it attached assets for 1.234.0
We deleted the release
j
Yikes. Sorry to read.
e
Have a pretty robust rewrite of our release process in the works
Will be testing today
šŸ™Œ 1
Related PR
Open in Slack
PreviousNext
Powered by