v0.16.0 release doesn't have prebuilt binaries

[rootulp]

Context

https://github.com/celestiaorg/celestia-node/releases/tag/v0.16.0 doesn't have prebuilt binaries.

Problem

Looks like integration tests keep failing on https://github.com/celestiaorg/celestia-node/actions/runs/10685447212 so version_bump and goreleaser never get triggered

Proposal

1. [short term] keep retrying CI until it succeeds
2. [medium term] maybe make version bump not depend on integration tests b/c they're flaky
3. [long term] fix the flaky integration tests

An alternative short term solution is to manually attach the prebuilt binaries. We've had to do that a lot on celestia-app b/c goreleaser config issues so we have a guide.

[renaynay]

Should be fixed now @rootulp

[rootulp]

https://github.com/celestiaorg/celestia-node/releases/tag/v0.16.0

[renaynay]

Oh whoops sorry I thought our CI ran properly 😬

[Halimao]

How is this issue going now? Still have trouble in downloading prebuilt binaries with bash -c "$(curl -sL https://docs.celestia.org/celestia-node.sh)"

--2024-10-03 02:49:34--  https://github.com/celestiaorg/celestia-node/releases/download/v0.16.0/celestia-node_Linux_x86_64.tar.gz
Resolving github.com (github.com)... 140.82.114.3
Connecting to github.com (github.com)|140.82.114.3|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2024-10-03 02:49:34 ERROR 404: Not Found.

[jcstein]

v0.17.1 doesn't either

[jcstein]

Reported from devrel telegram chat:

"and the doc says testnet is celestia-node v0.18.2-mocha, but that version docker image not exists"

[hyacinthus]

Yes, I need the docker image :)

[renaynay]

Our CI (goreleaser) has been fixed on recent releases, and v0.16.0 is now outdated on both arabica and mocha and will become outdated tomorrow on mainnet as well.

[rootulp]

FYI a release from yesterday doesn't have prebuilt binaries: https://github.com/celestiaorg/celestia-node/releases/tag/v0.20.2-arabica.

GoReleaser gets confused when fetching the latest tag for a particular commit if one commit has multiple tags (i.e. v2.0.0-mocha, v2.0.0-arabica). To temporarily workaround, celestia-app plans on creating releases on distinct commits. But it looks like celestia-node had a different problem for the v0.20.2-arabica b/c GoReleaser job was skipped: https://github.com/celestiaorg/celestia-node/actions/runs/11894453531/job/33141724905

[cristaloleg]

That's interesting, thanks for the info! I will take a look tomorrow.

[jcstein]

is this related to #3938 ?