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

[dependabot]

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

Changelog

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

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

• 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

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Looks like github.com/zclconf/go-cty-yaml is up-to-date now, so this is no longer needed.