v2.0.3

[pelletier]

This version has compatibility issues with Go <= 1.17. Though go-toml doesn't officially support Go less than 2 versions old, a new version has been released with a backward-compatible fix: https://github.com/pelletier/go-toml/releases/tag/v2.0.5.

What's Changed

Fixed bugs

• Encode: define and fix newlines behavior when using omitempty by @pelletier in Encode: define and fix newlines behavior when using omitempty  #798
• Encode: don't inherit omitempty by @pelletier in Encode: don't inherit omitempty #803
• Decode: error on array table mismatched type by @pelletier in Decode: error on array table mismatched type #804

Other changes

• build(deps): bump github.com/stretchr/testify from 1.7.2 to 1.8.0 by @dependabot in build(deps): bump github.com/stretchr/testify from 1.7.2 to 1.7.4 #793 build(deps): bump github.com/stretchr/testify from 1.7.4 to 1.7.5 #794 build(deps): bump github.com/stretchr/testify from 1.7.5 to 1.8.0 #795
• Go 1.19 by @pelletier in Go 1.19 #802

Full Changelog: v2.0.2...v2.0.3

---

This discussion was created from the release v2.0.3.

[sagikazarmark]

Looks like this upgrade broke a few tests in Viper: spf13/viper#1417

Haven't looked closer yet, so I can't say for sure what's the problem.

[pelletier]

This release cleans up the newline behavior of the encoder. After a quick look it seems like viper is testing for string equality of the output with a hardcoded string.

Before:

key = 'value'
list = ['item1', 'item2', 'item3']
[map]
key = 'value'

[nested_map]
[nested_map.map]
key = 'value'
list = ['item1', 'item2', 'item3']

After:

key = 'value'
list = ['item1', 'item2', 'item3']

[map]
key = 'value'

[nested_map]
[nested_map.map]
key = 'value'
list = ['item1', 'item2', 'item3']

The new output does not have the extra two new lines at the end, and more consistent spacing between blocks.

Seems like the upgrade is a matter of updating the expected string for the test.

[sagikazarmark]

Thanks for the explanation!

[pelletier]

This version has compatibility issues with Go <= 1.17. Though go-toml doesn't officially support Go less than 2 versions old, a new version has been released with a backward-compatible fix: https://github.com/pelletier/go-toml/releases/tag/v2.0.5.