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

build: switch to using Go 1.18 for CI in go.mod #1850

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

Roasbeef
Copy link
Member

In this commit, we switch to using Go 1.18 everywhere. This is a
deviation from our typical "last 2 versions" rule. Switching now gives
us access to the new type params feature immediately, versus near the
end of this year. With this change we'd also be able to start using the
new std lib fuzzing features as well.

In this commit, we switch to using Go 1.18 everywhere. This is a
deviation from our typical "last 2 versions" rule. Switching now gives
us access to the new type params feature immediately, versus near the
end of this year. With this change we'd also be able to start using the
new std lib fuzzing features as well.
@guggero
Copy link
Collaborator

guggero commented Apr 27, 2022

This needs a change in the Makefile as well, since go get is deprecated in go 1.18 and needs to be replaced with go install.

go get is no longer used to install or build things. Use go install
instead.  Also specify a version so the module's go.mod is not
touched when installing the CI tools.
@coveralls
Copy link

Pull Request Test Coverage Report for Build 2234921126

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • 1 unchanged line in 1 file lost coverage.
  • Overall coverage increased (+0.03%) to 54.298%

Files with Coverage Reduction New Missed Lines %
btcutil/gcs/gcs.go 1 81.25%
Totals Coverage Status
Change from base Build 2186219467: 0.03%
Covered Lines: 25191
Relevant Lines: 46394

💛 - Coveralls

@Roasbeef
Copy link
Member Author

So decided to hold off on this for a bit, influenced by comments from @chappjc. I updated that usage in the musig2 PR to be as compact at the call site as it would be w/ generics, but at the cost of some added function definitions.

@Roasbeef
Copy link
Member Author

Roasbeef commented Oct 8, 2024

Holding off on this for now, as we need to decide on a process for deciding when to update the Go version pinned for btcd, many downstream projects depend on it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants