chore: update Go toolchain to 1.26.4#20
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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
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.
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Fork-only simulation of the future-standard automatically generated Go toolchain baseline update PR.
This PR was created by GitHub Actions using
GITHUB_TOKEN, so the author should begithub-actions[bot]. The base branch intentionally simulates an old but post-volcano-sh#391-style Go baseline:go.modis the source of truth, workflows already usego-version-file: go.mod, and Dockergolang:*builder tags are aligned withgo.mod. The head branch was generated by the workflow and updates the project back to Go 1.26.4.Which issue(s) this PR fixes:
NONE
Special notes for your reviewer:
GITHUB_TOKEN.go mod tidy,git diff --check, exact 4-file changed list, and final tree comparison againstupstream/main..github/workflows/*; GitHub rejects those workflow-file pushes fromGITHUB_TOKENunless a separate token/app has workflow-file permission. Future regular Go baseline updates should not need workflow file changes because chore: update Go toolchain to 1.26.4 volcano-sh/agentcube#391 already moved setup-go togo-version-file: go.mod.Does this PR introduce a user-facing change?: