Update golang version to 1.26.1 to avoid vulnerability alerts.#628
Open
liushilongbuaa wants to merge 1 commit intosonic-net:masterfrom
Open
Update golang version to 1.26.1 to avoid vulnerability alerts.#628liushilongbuaa wants to merge 1 commit intosonic-net:masterfrom
liushilongbuaa wants to merge 1 commit intosonic-net:masterfrom
Conversation
|
|
Contributor
|
/azp run |
liushilongbuaa
changed the title
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR appears to update the repository’s Go toolchain/versioning and dependency metadata (likely as part of a vulnerability/security hardening effort) and adjusts build tooling behavior.
Changes:
- Update Go version in
go.modand Azure Pipelines. - Tidy
go.sumentries for removed/updated transitive dependencies. - Add
-buildvcs=falsetogo installinvocations in the Makefile.
Reviewed changes
Copilot reviewed 3 out of 4 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| go.sum | Removes stale sums for older transitive module versions. |
| go.mod | Updates Go version declaration and adjusts dependency direct/indirect classification. |
| azure-pipelines.yml | Bumps Go version and adds a Go install step for CI jobs. |
| Makefile | Disables VCS stamping for select go install commands. |
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Signed-off-by: shilongliu <shilongliu@microsoft.com>
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
|
This will not work as the go in gnmi container is based on bookworm right now (<= go 1.19) or even if we migrate to triie, go can at most be 1.24 unless we create new build recipes. |
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.
Why I did it
I'm working to fix GO-2026-4337.
before go1.24.13, from go1.25.0-0 before go1.25.7, from go1.26.0-rc.1 before go1.26.0-rc.3
How I did it
How to verify it
Which release branch to backport (provide reason below if selected)
Description for the changelog
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)