container-diff bug: release artefacts are missing

Expected behavior

Release should contain binary artefacts

Actual behavior

https://github.com/GoogleContainerTools/container-diff/releases/tag/v0.19.0 is only providing source

Feb 22 '24 11:02 mbevc1

This is important as it breaks my CI wanting to do a Scoop package of container-diff

Feb 23 '24 09:02 alkuzad

v0.19.0 is also missing from https://storage.googleapis.com/container-diff/. Even the latest there is from 2021.

Feb 27 '24 12:02 gg-kialo

Could we please get this re-released with the missing artefacts?

Feb 27 '24 12:02 mbevc1

it's possible the cloud build trigger is dead, I can't seem to trace back what project owns it. I'm only a very minor maintainer. v0.19.0 may only provide source for now... if someone wants to move the build to github actions or goreleaser or something, I can approve PRs

Feb 28 '24 22:02 loosebazooka

If switching I'd suggest using go-releaser :)

Feb 28 '24 23:02 mbevc1

@loosebazooka would goreleaser be something you'd be happy to approve?

Mar 11 '24 21:03 mbevc1

So there are a couple things I'm exploring because:

The build for this project is already a bit weird, and there are no current "real" maintainers.
This was a dependency for another project (container-structure-test), but I've removed that dependency and now there aren't any pressing reasons for me to continue to look at this project (and I presume no one else really is).
I'm thinking about archiving this, rather that letting it fall into a poor state.

Current user options appear to be:

See if a more recent, maintained project works for you: diffoci
Users fork this and find some active users who can help maintain it.

Mar 12 '24 01:03 loosebazooka