Docker: Use more aggressive inlining for higher efficiency#5242
Merged
Docker: Use more aggressive inlining for higher efficiency#5242
Conversation
Collaborator
Author
|
Member
|
为啥要把 latest 改为 1.25 |
Collaborator
Author
非 Docker 的 build 工作流在 Set up Go 那步 Docker 没有这一步，所以都是 latest 偷懒 
|
Member
|
改回去吧，Go 1.25+ 应该都没有前几个那么刺激的更新了，不会换了 Go 1.26 就编译不了 #5024 (comment) |
Collaborator
Author
|
okk |
This was referenced Dec 1, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
同步
#5026