- New upstream release 1.73
- Perform correct stripping of leading white space in literal/folded text
blocks (GH#44, CPAN RT#56045)
- Fix compatibility with Test::Builder 0.94 in test shim
The tests fall back to JSON::PP if JSON::MaybeXS is not available.
Reason for thus condition is this building autotools: JSON::MaybeXS
requires Compress::LZF that requires liblzf that requires autotools.
And autotools require modules whose packages are built by
Module::Install that requires YAML::Tiny that goes back JSON::MaybeXS
tests.
- New upstream release 1.69
- Tests no longer print to stderr unnecessarily; this makes core perl builds
(where this distribution is included as CPAN-Meta-YAML) a little quieter
- The Test::More dependency has been reduced to 0.88 by emulating 'subtest'
for those tests that need it
- New upstream release 1.67
- Instead of erroring on duplicate keys found in a hash (introduced in
version 1.63), now we only warn; this fixes an issue in Strawberry Perl
(via CPAN::Meta::YAML) when parsing a configuration file
- Updated File::Temp test prereq to 0.19 for 'newdir'
- New upstream release 1.66
- Removed bundled Test::TempDir::Tiny to rely on File::Temp for temporary
directories during testing
- Revert to ExtUtils::MakeMaker flow
- New upstream release 1.64
- Remove silencing of any errors encountered while loading Scalar::Util
(GH#33)
- Now using JSON::MaybeXS in tests instead of JSON.pm
- Use %license
- New upstream release 1.63
- Incorrect error messages fixed, when $@ is clobbered when Carp wasn't
loaded (GH#30, GH#31)
- Now checking for, and erroring on, duplicate keys found in a hash (GH#32)
- New upstream release 1.60
- Numeric values are now quoted whenever they've been used as a string,
which fixes inconsistent behaviour seen with numeric values, due to
differences between the XS and pure-perl variants of Data::Dumper
(GitHub Issue #24)
- Numeric hash keys are now always quoted
- New upstream release 1.58
- 1.57 omitted a change entry for the following change:
Incompatible change:
- Previously, YAML::Tiny was sloppy about file encodings; it is now strict
- The 'read' method and 'LoadFile' function expect UTF-8 encoded files
- The 'write' method and 'DumpFile' function produce UTF-8 encoded files
- The 'read_string' and 'write_string' methods and the 'Load' and 'Dump'
functions expect or generate (decoded) character data
- New upstream release 1.57
Incompatible change:
- Previously, some errors would throw exceptions and some would return the
error condition in $YAML::Tiny::errstr, but now all errors throw
exceptions; use of $errstr and the errstr method are deprecated
Fixed:
- Fixed write method to encode YAML file with UTF-8
- Improved SYNOPSIS and documentation of new
Testing:
- Tests have been cleaned up and reorganized
- Test coverage has been significantly improved
- Package docs CONTRIBUTING and README.md
- Update dependencies as needed
