HCL is the HashiCorp configuration language.
Full Changelog: https://github.com/hashicorp/hcl/compare/v2.19.1...v2.20.0
Full Changelog: https://github.com/hashicorp/hcl/compare/v2.19.0...v2.19.1
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.
https://
at the start of a URL known to use that scheme. (#617)any
keyword, avoiding an incorrect panic at runtime. (#625)HCL now uses a newer version of the upstream cty
library which has improved treatment of unknown values: it can now track additional optional information that reduces the range of an unknown value, which allows some operations against unknown values to return known or partially-known results. (#590)
Note: This change effectively passes on cty
's notion of backward compatibility whereby unknown values can become "more known" in later releases. In particular, if your caller is using cty.Value.RawEquals
in its tests against the results of operations with unknown values then you may see those tests begin failing after upgrading, due to the values now being more "refined".
If so, you should review the refinements with consideration to the cty
refinements docs and update your expected results to match only if the reported refinements seem correct for the given situation. The RawEquals
method is intended only for making exact value comparisons in test cases, so main application code should not use it; use Equals
instead for real logic, which will take refinements into account automatically.
ext/typeexpr: Modify the Defaults functionality to implement additional flexibility. HCL will now upcast lists and sets into tuples, and maps into objects, when applying default values if the applied defaults cause the elements within a target collection to have differing types. Previously, this would have resulted in a panic, now HCL will return a modified overall type. (https://github.com/hashicorp/hcl/pull/574)
Users should return to the advice provided by v2.14.0, and apply the go-cty convert functionality after setting defaults on a given cty.Value, rather than before.
hclfmt: Avoid rewriting unchanged files. (https://github.com/hashicorp/hcl/pull/576)
hclsyntax: Simplify the AST for certain string expressions. (https://github.com/hashicorp/hcl/pull/584)