Modernize project to Go 1.25 and address security vulnerabilities - #225
Merged
Merged
Conversation
Updated Go base image to version 1.25 and removed image digest pinning for multi-architecture support.
Collaborator
Author
|
GO promises backward compatibility, and also, there are no changes between 1.24 and 1.25 that we are using in our action. Tested with the new version in my org repos and it is working. @lizziemac @beverts312 |
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
1 participant
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.
GO version bumped, 1.24 -> 1.25 in order to bump crypto package 0.45 -> 0.53
Warn: Project is vulnerable to: GO-2026-5005
Warn: Project is vulnerable to: GO-2026-5006
Warn: Project is vulnerable to: GO-2026-5013
Warn: Project is vulnerable to: GO-2026-5014
Warn: Project is vulnerable to: GO-2026-5015
Warn: Project is vulnerable to: GO-2026-5016
Warn: Project is vulnerable to: GO-2026-5017
Warn: Project is vulnerable to: GO-2026-5018
Warn: Project is vulnerable to: GO-2026-5019
Warn: Project is vulnerable to: GO-2026-5020
Warn: Project is vulnerable to: GO-2026-5021
Warn: Project is vulnerable to: GO-2026-5023
Warn: Project is vulnerable to: GO-2026-5033