Backport: deps: migrate mapstructure to go-viper (#22581) #22780
Conversation
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
* deps: migrate mapstructure to go-viper * go mod tidy * add changelog * fix test * go mod tidy * fix test * fix test * go mod tidy
github-actions
bot
added
theme/api
LakshmiNarayananDesikan
added
the
pr/no-changelog
LakshmiNarayananDesikan
changed the title
LakshmiNarayananDesikan
added
pr/no-backport
pr/dependencies
Manishakumari-hc
approved these changes
Sep 17, 2025
Manishakumari-hc
approved these changes
Sep 17, 2025
Manishakumari-hc
approved these changes
Sep 17, 2025
LakshmiNarayananDesikan
merged commit 15aa895
into
release/1.21.x
282 of 337 checks passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Description
Backport of #22581
https://github.com/mitchellh/mapstructure is now a public archive, this PR aims to migrate to a fork of it https://github.com/go-viper/mapstructure (v2) which is maintained and gets frequent security patches.
Ref: PSA-2107
Testing & Reproduction steps
Links
PR Checklist
PCI review checklist
I have documented a clear reason for, and description of, the change I am making.
If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
If applicable, I've documented the impact of any changes to security controls.
Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.