Bump github.com/zclconf/go-cty-yaml from 1.0.2 to 1.2.0

[dependabot]

Bumps github.com/zclconf/go-cty-yaml from 1.0.2 to 1.2.0.

Changelog

Sourced from github.com/zclconf/go-cty-yaml's changelog.

1.2.0 (December 17, 2025)

• The YAML decoder now has more complete support for tag:yaml.org,2002:merge, including support for merging a sequence of mappings rather than just a single mapping.

  Unfortunately the specification for this tag is terse and incomplete, and other existing implementations disagree even with the few behaviors that are described in the specification, so this library implements behavior that matches existing implementations while diverging slightly from the spec:

  • The untagged scalar value << is resolved as tag:yaml.org,2002:merge only in the mapping key position. In all other positions it's resolved as a normal string, "<<". Writing out the tag explicitly instead of using the shorthand is allowed in mapping key position and rejected as an error in all other positions.
  • Multiple merge keys can appear in the same mapping, and will each be handled separately as if they had all been written as a single merge.
  • Later mentions of a key override earlier mentions of a key in all cases. This is the main deviation from the spec text: the spec requires that the earliest mention of each key takes priority when merging, but that is the opposite of the normal behavior for duplicate keys in a mapping (without merging) and other implementations seem to ignore that exception.

  There are a few other implementations that disagree with what this library implements. That's unfortunate, but unavoidable because existing implementations are in conflict with one another already. The choices in this implementation were based on a survey of various other popular implementatins and will not be changed in a breaking way after this release.

1.1.0 (October 2, 2024)

• The YAML decoder now exactly follows the YAML specification when resolving the implied YAML tags for integers. (#6)

  The new implementation matches the patterns in the specification, but it now has stricter integer resolution than the previous release. The primary goal of this library is to translate valid YAML syntax to and from cty's type system and so deviation from the YAML grammar is treated typically as a bug to be fixed even if that means a change in behavior for existing callers that were dealing in invalid input. This further improves earlier work done in v1.0.2, which didn't quite match the spec.

  In particular:

  • Scalars containing underscores can no longer be resolved as integers.
  • Octal and hexadecimal sequences must now start with exactly Oo and 0x respectively to be resolved as integers; a leading sign (+ or -) is accepted only for the decimal integer and float patterns.

  The YAML tag resolution process infers an implied type tag for each scalar value that isn't explicitly tagged. go-cty-yaml then uses the YAML tags (whether implied or explicit) to decide which cty type to use for each value in the result.

  The scalar values that are no longer resolved as numbers will now all be resolved as strings instead, and so calling applications can perform further parsing and transformation on the resulting strings to accept forms outside of those in the YAML specification, if required.

1.0.3 (November 2, 2022)

• The YAMLDecodeFunc cty function now correctly handles both entirely empty documents and explicit top-level nulls. Previously it would always return an unknown value in those cases; it now returns a null value as intended. (#7)

Commits

• 85d6bca v1.2.0 release
• 229f481 Allow a !!merge key to be used with a sequence of mappings
• 5da71a8 Add GitHub funding metadata
• 0e40a15 v1.1.0 release
• a2572e6 Implicit number recognition pattern now matches YAML specifications
• cb2841a v1.0.3 release
• c591969 YAMLDecodeFunc: handle null values correctly
• 14b7afb go.mod: Update for newer Go version conventions
• See full diff in compare view

[whymarrh]

@dependabot rebase

[whymarrh]

Thanks, buddy!