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

drop Go 1.22 and require Go 1.23.0 or later #876

Merged
merged 1 commit into from
Nov 17, 2024

Conversation

mvdan
Copy link
Member

@mvdan mvdan commented Sep 15, 2024

(see commit message)

@lu4p
Copy link
Member

lu4p commented Oct 21, 2024

If we drop go 1.22 we should also drop it from ci. Also isn't something weird going on here, that ci is not failing on 1.22?

CI is failing on Ubuntu 1.23.

@mvdan
Copy link
Member Author

mvdan commented Oct 21, 2024

Well spotted regarding 1.22.

I'm still trying to figure out the third party test failures.

@mvdan
Copy link
Member Author

mvdan commented Nov 16, 2024

Also isn't something weird going on here, that ci is not failing on 1.22?

That would be https://go.dev/doc/toolchain kicking in by default.

This lets us start taking advantage of featurs from Go 1.23,
particularly tracking aliases in go/types and iterators.

Note that we need to add code to properly handle or skip over the new
*types.Alias type which go/types produces for Go type aliases.
Also note that we actually turn this mode off entirely for now,
due to the bug reported at https://go.dev/issue/70394.

We don't yet remove our own alias tracking code yet due to the above.
We hope to be able to remove it very soon.
@mvdan
Copy link
Member Author

mvdan commented Nov 16, 2024

@lu4p @pagran this should be finally ready to review. Note that the new alias tracking stuff is entirely disabled for now due to golang/go#70394. That was causing lots of test failures, both in our tests and in the protobuf module.

@lu4p lu4p merged commit 30357af into burrowers:master Nov 17, 2024
4 checks passed
@mvdan mvdan deleted the drop-go1.22 branch November 18, 2024 23:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants