Bump the gomod-minor group with 2 updates

[dependabot]

Bumps the gomod-minor group with 2 updates: github.com/hashicorp/hcl/v2 and github.com/zclconf/go-cty.

Updates github.com/hashicorp/hcl/v2 from 2.16.2 to 2.20.0

Release notes

Sourced from github.com/hashicorp/hcl/v2's releases.

v2.20.0

What's Changed

• Namespaced functions by @​jbardin in hashicorp/hcl#639
• fix: fix NameRange for namespaced functions by @​ansgarm in hashicorp/hcl#651
• prefer iterator error over for_each by @​DanielMSchmidt in hashicorp/hcl#656
• Create an error type for unknown function diags by @​jbardin in hashicorp/hcl#657
• Typo fix in spec.md by @​elliotbonneville in hashicorp/hcl#652
• hclwrite: Fix formatting of namespaced functions by @​radeksimko in hashicorp/hcl#658
• Run unit tests on macOS by @​radeksimko in hashicorp/hcl#660
• Fix license headers by @​radeksimko in hashicorp/hcl#659
• Add make targets for common checks + fixes by @​radeksimko in hashicorp/hcl#661
• Use new make targets in CI by @​radeksimko in hashicorp/hcl#663

New Contributors

• @​ansgarm made their first contribution in hashicorp/hcl#651
• @​DanielMSchmidt made their first contribution in hashicorp/hcl#656
• @​elliotbonneville made their first contribution in hashicorp/hcl#652

Full Changelog: hashicorp/hcl@v2.19.1...v2.20.0

v2.19.1

What's Changed

• hcldec must use WithoutOptionalAttributesDeep by @​jbardin in hashicorp/hcl#635

Full Changelog: hashicorp/hcl@v2.19.0...v2.19.1

v2.18.1

Bugs Fixed

• hclsyntax: Conditional expressions will no longer panic when one or both of their results are "marked", as is the case for situations like how HashiCorp Terraform tracks its concept of "sensitive values". (#630)

v2.18.0

Enhancements

• HCL now uses the tables from Unicode 15 when performing string normalization and character segmentation. HCL was previously using the Unicode 13 tables.

  For calling applications where consistent Unicode support is important, consider also upgrading to Go 1.21 at the same time as adopting HCL v2.18.0 so that the standard library unicode tables (used for case folding, etc) will also be from Unicode 15.

v2.17.1

Enhancements

• hclsyntax: When evaluating string templates that have a long known constant prefix, HCL will truncate the known prefix to avoid creating excessively-large refinements. String prefix refinements are intended primarily for relatively-short fixed prefixes, such as https:// at the start of a URL known to use that scheme. (#617)
• ext/tryfunc: The "try" and "can" functions now handle unknown values slightly more precisely, and so can return known values in more situations when given expressions referring to unknown symbols. (#622)

Bugs Fixed

• ext/typeexpr: Will no longer try to refine unknown values of unknown type when dealing with a user-specified type constraint containing the any keyword, avoiding an incorrect panic at runtime. (#625)
• ext/typeexpr: Now correctly handles attempts to declare the same object type attribute multiple times by returning an error. Previously this could potentially panic by creating an incoherent internal state. (#624)

... (truncated)

Changelog

Sourced from github.com/hashicorp/hcl/v2's changelog.

v2.20.0 (February 29, 2024)

Enhancements

• Support for namespaced functions (#639)

Bugs Fixed

• ext/dynblock: if iterator is invalid return this error instead of consequential errors (#656)

v2.19.0 (October 16, 2023)

Enhancements

• ext/dynblock: dynblock.Expand now supports an optional hook for calling applications to check and potentially veto (by returning error diagnostics) particular for_each values. The behavior is unchanged for callers that don't set the new option. (#634)

Bugs Fixed

• hclsyntax: Further fixes for treatment of "marked" values in the conditional expression, and better tracking of refined values into the conditional expression results, building on the fixes from v2.18.1. (#633)

v2.18.1 (October 5, 2023)

Bugs Fixed

• hclsyntax: Conditional expressions will no longer panic when one or both of their results are "marked", as is the case for situations like how HashiCorp Terraform tracks its concept of "sensitive values". (#630)

v2.18.0 (August 30, 2023)

Enhancements

• HCL now uses the tables from Unicode 15 when performing string normalization and character segmentation. HCL was previously using the Unicode 13 tables.

  For calling applications where consistent Unicode support is important, consider also upgrading to Go 1.21 at the same time as adopting HCL v2.18.0 so that the standard library unicode tables (used for case folding, etc) will also be from Unicode 15.

v2.17.1 (August 30, 2023)

Enhancements

• hclsyntax: When evaluating string templates that have a long known constant prefix, HCL will truncate the known prefix to avoid creating excessively-large refinements. String prefix refinements are intended primarily for relatively-short fixed prefixes, such as https:// at the start of a URL known to use that scheme. (#617)
• ext/tryfunc: The "try" and "can" functions now handle unknown values slightly more precisely, and so can return known values in more situations when given expressions referring to unknown symbols. (#622)

Bugs Fixed

• ext/typeexpr: Will no longer try to refine unknown values of unknown type when dealing with a user-specified type constraint containing the any keyword, avoiding an incorrect panic at runtime. (#625)
• ext/typeexpr: Now correctly handles attempts to declare the same object type attribute multiple times by returning an error. Previously this could potentially panic by creating an incoherent internal state. (#624)

v2.17.0 (May 31, 2023)

Enhancements

... (truncated)

Commits

• 57f8bbf update CHANGELOG.md for v2.20
• 21a05d5 Merge pull request #663 from hashicorp/ci-workflow-updates
• 1f6a0f7 Use make targets in CI
• c152f81 Merge pull request #661 from hashicorp/add-makefile
• 76bf60b Merge pull request #659 from hashicorp/fix-license-headers
• bd58136 Merge pull request #660 from hashicorp/ci-test-on-macos
• 3cf7572 Add make targets for common checks + fixes
• 63380ba Update CHANGELOG.md
• 6055ebc Update CHANGELOG.md
• b079b8b Update changelog
• Additional commits viewable in compare view

Updates github.com/zclconf/go-cty from 1.13.1 to 1.14.3

Release notes

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

v1.13.2

• cty: IndexStep.Apply will no longer panic if given a marked collection to traverse through. (#160).

Changelog

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

1.14.3 (February 29, 2024)

• msgpack: Fixed edge-case bug that could cause loss of floating point precision when round-tripping due to incorrectly using a MessagePack integer to represent a large non-integral number. #176
• cty: Fixed some false-negative numeric equality test results by comparing numbers as integers when possible. #176

1.14.2 (January 23, 2024)

• convert: Converting from an unknown map value to an object type now correctly handles the situation where the map element type disagrees with an optional attribute of the target type, since when a map value is unknown we don't yet know which keys it has and thus cannot predict what subset of the elements will get converted as attributes in the resulting object. (#175)

1.14.1 (October 5, 2023)

• cty: It's now valid to use the Refine method on cty.DynamicVal, although all refinements will be silently discarded. This replaces the original behavior of panicking when trying to refine cty.DynamicVal.

• cty: Value.Range will now return a clearer panic message if called on a marked value. The "value range" concept is only applicable to unmarked values because not all of the ValueRange functions are able to propagate marks into their return values, due to returning Go primitive types instead of new cty.Value results.

  Callers that use marks must, as usual, take care to unmark them before exporting values into "normal" Go types, and then explicitly re-apply the marks to their result as appropriate. Applications that make no use of value marks, and library callers that exclude marked values from what they support, can safely ignore this requirement.

1.14.0 (August 30, 2023)

This release updates the supported version of Unicode from Unicode 13 to Unicode 15. This is a backwards-compatible change that means that cty supports normalization and segmentation of strings containing new Unicode characters. The algorithms for normalization and segmentation themselves are unchanged.

If you use cty in an application that cares about consistent Unicode support, you should upgrade to Go 1.21 at the same time as updating to cty v1.14, because that will then also update the Unicode tables embedded in the Go standard library (used for case folding, etc).

• cty: The cty.String type will now normalize incoming string values using the Unicode 15 normalization rules.
• function/stdlib: The various string functions which split strings into individual characters as part of their work will now use the Unicode 15 version of the text segmentation algorithm to do so.

1.13.3 (August 24, 2023)

• msgpack: As a compromise to avoid unbounded memory usage for a situation that some callers won't take advantage of anyway, the MessagePack decoder has a maximum length limit on encoded unknown value refinements. For consistency, the encoder will now truncate string prefix refinements if necessary to avoid making the encoded refinements too long. (#167)

  This is consistent with the documented conventions for serializing refinements -- that we can potentially lose detail through serialization -- but in this case we are still able to preserve shorter string prefixes, whereas other serializations tend to just discard refinement information altogether.

1.13.2 (May 22, 2023)

• cty: IndexStep.Apply will no longer panic if given a marked collection to traverse through. (#160).

Commits

• 304e4a8 v1.14.3 release
• 50ce6d3 Update CHANGELOG.md
• 1e9442d don't use compact floats in msgpack
• a0315a5 Use integer comparison for equality
• 1348b69 Prepare for possible future v1.14.3 release
• 5917c03 Prepare for v1.14.2 release.
• 72902f2 Update CHANGELOG.md
• 864b88d convert: prevent invalid types in dynamicReplace
• d279406 Prepare for a possible future v1.14.2 release
• 7152062 Release v1.14.1
• Additional commits viewable 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

The group that created this PR has been removed from your configuration.