Skip to content

switch to viper's maintained mapstructure instead of mitchellh's#596

Closed
aladeeb wants to merge 2 commits intovouch:masterfrom
aladeeb:fix/use-go-viper-mapstructure-instead-of-mitchellh
Closed

switch to viper's maintained mapstructure instead of mitchellh's#596
aladeeb wants to merge 2 commits intovouch:masterfrom
aladeeb:fix/use-go-viper-mapstructure-instead-of-mitchellh

Conversation

@aladeeb
Copy link

@aladeeb aladeeb commented May 4, 2025

This PR introduces a fix for a breaking change introduced in viper minor version bump up (v1.20). It was failing to build the package with the old mapstructure module. So, I've moved from using mitchellh's mapstructure as it's deprecated to the maintained one by go-viper.

This is according to v1.20 release notes: https://github.com/spf13/viper/blob/master/UPGRADE.md#breaking-githubcommitchellhmapstructure-depedency-replaced

I had to use github.com/go-viper/mapstructure/v2 instead of github.com/mitchellh/mapstructure

@aladeeb aladeeb changed the title switch to viper mapstructure instead of mitchellh's switch to viper's maintained mapstructure instead of mitchellh's May 4, 2025
@aaronpk
Copy link
Collaborator

aaronpk commented Jul 16, 2025

Thanks for this, but I merged this one which was a smaller change: #598

@aaronpk aaronpk closed this Jul 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants