v0.10.5

• 96dfb2c fix: Yamagiconf now accepts no value for zero-value bool (similar to all other Go types) instead of returning ErrYAMLBadBoolLiteral.
• ebcd2a3 chore: Dependencies are upgraded.

v0.10.4

• 1b12dc0 chore: Upgrade dependencies.

v0.10.3

• a37a3c3 fix: Exported struct fields are now properly validated even if the struct implements encoding.TextUnmarshaler.
• aaca598 fix: Load and LoadFile no longer panic when invoking Validate on encoding.TextUnmarshaler interface implementations.
• 64d972c fix: Load and LoadFile now return a new error ErrYAMLNonStrOnTextUnmarsh when a non-string YAML value is assigned to a Go type that implements encoding.TextUnmarshaler.

v0.10.2

• e2ed2aa fix: Type restrictions are no longer applied to named types that implement yaml.Unmarshaler or encoding.TextUnmarshaler interfaces. Previously, types like type ImplementsTextUnmarshaler int would not be accepted.

v0.10.1

• aa38c1e fix: The method Validate will now also be invoked for values a pointer to which implements the Validator interface.

v0.10.0

• ceef608 feat: Improve sentinel error naming consistency.

v0.9.0

• d421bcb !feat: Anchors with implicit zero value such as foo: &bar are no longer allowed and will return ErrYAMLAnchorNoValue. Use explicit zero value such as foo: &bar ''.
• 08354a0 fix: No panic when aliasing a composite value (such as an array) any more.
• b7210b9 fix: ErrBadBoolLiteral is no longer returned for aliases.

v0.8.0

• c1b5861 feat: Unused anchors (no alias referencing a defined anchor) are now forbidden.

v0.7.0

• 716634f feat: Introduced function Validate which validates a given variable without parsing YAML.

v0.6.1

• f6b28cd fix: Load and LoadFile will now return error for env tag on a field of a primitive named type that implements the yaml.Unmarshaler interface because for a type like type MyString string that implements yaml.Unmarshaler env unmarshaling will just copy the env value to the underlying string potentially bypassing any validation logic that might have been defined in UnmarshalYAML. Therefore it's safer to use encoding.TextUnmarshaler instead since it's supported by both the env and the yaml parsers.