[Feature Request]: implement celestia-node's handling of go version in CI #16
Labels
enhancement
New feature or request
Comments
ramin
added a commit
to ramin/go-da
that referenced
this issue
Nov 2, 2023
…hat version to output and uses in descendent workflows refs rollkit#16
5 tasks
tzdybal
pushed a commit
to ramin/go-da
that referenced
this issue
May 10, 2024
…hat version to output and uses in descendent workflows refs rollkit#16
tzdybal
pushed a commit
to ramin/go-da
that referenced
this issue
Sep 2, 2024
…hat version to output and uses in descendent workflows refs rollkit#16
tzdybal
pushed a commit
to ramin/go-da
that referenced
this issue
Sep 2, 2024
…hat version to output and uses in descendent workflows refs rollkit#16
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Implementation ideas
REF: celestiaorg/celestia-node#2806
This use of a CI step that sets the go version as an output allows us to have a single go version defined for the entire CI.
The text was updated successfully, but these errors were encountered: