Skip to content

chore(deps): replace mitchellh/mapstructure with go-viper/mapstructure/v2#59

Merged
mathieu-benoit merged 1 commit intoscore-spec:mainfrom
Abhishek9639:fix/443
Apr 8, 2026
Merged

chore(deps): replace mitchellh/mapstructure with go-viper/mapstructure/v2#59
mathieu-benoit merged 1 commit intoscore-spec:mainfrom
Abhishek9639:fix/443

Conversation

@Abhishek9639
Copy link
Copy Markdown
Contributor

Description

Swap out the archived mitchellh/mapstructure for the maintained go-viper/mapstructure/v2 fork. score-go is already at v1.13.0 which includes the same migration.

Changes:

  • Updated the import in internal/provisioners/provisioning.go.
  • Replaced mitchellh/mapstructure with go-viper/mapstructure/v2 in go.mod.
  • Ran go mod tidy.

What does this PR do?

mitchellh/mapstructure is archived and no longer maintained. This replaces it with the actively maintained fork, as discussed in score-spec/score-compose#443. The same migration was already done in score-go (score-spec/score-go#176), score-compose (score-spec/score-compose#450), and score-k8s (score-spec/score-k8s#280).

Types of changes

  • New chore (expected functionality to be implemented)

Checklist:

  • I've signed off with an email address that matches the commit author.

…e/v2

Replace the archived mitchellh/mapstructure with the maintained go-viper/mapstructure/v2 fork. score-go is already at v1.13.0 which includes the same migration.

Signed-off-by: Abhishek <abhishekup082@gmail.com>
@Abhishek9639
Copy link
Copy Markdown
Contributor Author

Hi @mathieu-benoit,

Opened the PR for the score-radius repo as well same mapstructure migration pattern. score-go was already at v1.13.0 here so only the direct dependency swap was needed.

Both score-k8s (#280) and score-radius (#59) are now ready for your review.
Let me know if anything needs to be changed.

Thanks!

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