Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request]: implement celestia-node's handling of go version in CI #16

Open
MSevey opened this issue Oct 24, 2023 · 0 comments
Open
Labels
enhancement New feature or request

Comments

@MSevey
Copy link
Contributor

MSevey commented Oct 24, 2023

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.

@MSevey MSevey added the enhancement New feature or request label Oct 24, 2023
@github-project-automation github-project-automation bot moved this to Backlog in Rollkit Oct 24, 2023
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
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
github-merge-queue bot pushed a commit that referenced this issue Sep 2, 2024
…hat version to output and uses in descendent workflows refs #16 (#19)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: No status
Development

No branches or pull requests

1 participant