Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade gopkg.in/yaml.v2 to gopkg.in/yaml.v3 #1264

Closed
wants to merge 1 commit into from
Closed

Upgrade gopkg.in/yaml.v2 to gopkg.in/yaml.v3 #1264

wants to merge 1 commit into from

Conversation

inteon
Copy link

@inteon inteon commented Dec 15, 2021

replacement PR of #1204

@github-actions
Copy link

👋 Thanks for contributing to Viper! You are awesome! 🎉

A maintainer will take a look at your pull request shortly. 👀

In the meantime: We are working on Viper v2 and we would love to hear your thoughts about what you like or don't like about Viper, so we can improve or fix those issues.

⏰ If you have a couple minutes, please take some time and share your thoughts: https://forms.gle/R6faU74qPRPAzchZ9

📣 If you've already given us your feedback, you can still help by spreading the news,
either by sharing the above link or telling people about this on Twitter:

https://twitter.com/sagikazarmark/status/1306904078967074816

Thank you! ❤️

@sagikazarmark
Copy link
Collaborator

@inteon Thanks for rebasing!

I asked the author of go-yaml about plans to release a new version. I'm not that familiar with it, but I'm a bit reluctant pulling in an untagged version.

Let's see what they say.

@sagikazarmark
Copy link
Collaborator

@inteon thanks for this PR! I decided to hide yaml v3 behind a build tag until there is more information available about an official release.

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