-
Notifications
You must be signed in to change notification settings - Fork 32
feat: support up to Go 1.18 #43
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
Conversation
|
ok, so the code modernization detection break things here... |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
aba48bb to
4f7700b
Compare
4d4ddf8 to
aed133b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the only thing left is to update the version badge in the README.
|
Does your code change about ANSI windows work if you cherry pick temporarily my commit into your branch ? |
|
I cherry-picked your commit but ran into a dependency issue. The cherry-pick worked fine, but when I run go mod tidy, it automatically upgrades from go 1.18 to go 1.23.0 because the dependencies require it: golang.org/x/sys@v0.34.0 requires go@1.23.0
golang.org/x/term@v0.33.0 requires go@1.23.0 |
|
Yes, I was worried about it |
|
@Andrei-hub11 could you tell me if this solves the issue? go mod tidy -go=1.18 |
|
The code can be used with old Go versions. The CI will also run tests for Go 1.18 and latest -rc versions.
The code can be used with old Go versions.
The CI will also run tests for Go 1.18 and latest -rc versions.
Fixed #42