Bump github.com/go-viper/mapstructure/v2 to v2.4.0 to address security concerns#1115
Merged
LandonTClipp merged 1 commit intovektra:v3from Sep 16, 2025
Merged
Conversation
…-3900 Signed-off-by: RainbowMango <qdurenhongcai@gmail.com>
Contributor
Author
|
cc @LandonTClipp |
Member
|
This is the second vulnerability of mapstructure in the last few months? What's going on? I'll get it released. |
Contributor
Author
|
Haha, as dependencies grow, such things will become more common. By the way, have you ever considered using Dependabot to take care of all these tasks? |
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.
Description
Bump github.com/go-viper/mapstructure/v2 to v2.4.0 to address security concerns. (GO-2025-3900).
Type of change
Version of Go used when building/testing:
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist