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

Update Go SDKs #4272

Merged
merged 5 commits into from
Feb 17, 2025
Merged

Update Go SDKs #4272

merged 5 commits into from
Feb 17, 2025

Conversation

fmeum
Copy link
Member

@fmeum fmeum commented Feb 13, 2025

What type of PR is this?

Other

What does this PR do? Why is it needed?

Update WORKSPACE to 1.24.0 to starting testing and bump the default SDK with Bzlmod to 1.23.6 in line with our policy to use the latest minor version of the oldest maintained release.

Which issues(s) does this PR fix?

Fixes #4267

Other notes for review

@fmeum
Copy link
Member Author

fmeum commented Feb 15, 2025

The remaining tests that fail are crypto tests. I would like to understand why they fail as this seems potentially problematic.

@jayconrod Do you happen to have an idea why we are seeing this?

Update WORKSPACE to 1.24.0 to starting testing and bump the default SDK with Bzlmod to 1.23.6 in line with our policy to use the latest minor version of the oldest maintained release.

This requires updating x/tools for WORKSPACE setups.
@fmeum fmeum requested review from tyler-french and linzhp and removed request for tyler-french February 17, 2025 08:41
@fmeum fmeum marked this pull request as ready for review February 17, 2025 08:41
@fmeum fmeum merged commit cdafba7 into master Feb 17, 2025
4 checks passed
@fmeum fmeum deleted the 4267-go1.24 branch February 17, 2025 19:12
@jayconrod
Copy link
Contributor

What were the failures? Not sure if there's an easy way for me to see past BuildKite runs.

Without looking in detail, most popular_repos exclusions are due to testdata usage that's difficult to automate. Crypto also tends to use assembly, and we might run into unsupported edge cases there.

@fmeum
Copy link
Member Author

fmeum commented Feb 18, 2025

Turns out that Go 1.24 disallowed key sizes used by old crypto tests (old as in until a week ago). Fixed by updating x/crypto.

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.

nogo skips analyzers when using go1.24: (unsupported version: 2); please report an issue
3 participants