summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDaniel Schmidt <danielmschmidt92@gmail.com>2024-02-16 15:22:05 +0100
committerDaniel Schmidt <danielmschmidt92@gmail.com>2024-02-16 15:22:05 +0100
commitb079b8b78743e7bca2ef20b876e16fb0af0e962a (patch)
treec1e2cfadac5f0cea8b9cf425b3b434b332bc6820
parenta7f9ab5f338cecf99d46b98dc43450d1fcb96373 (diff)
Update changelog
-rw-r--r--CHANGELOG.md10
1 files changed, 8 insertions, 2 deletions
diff --git a/CHANGELOG.md b/CHANGELOG.md
index f3fe93d..6e018a6 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,11 @@
# HCL Changelog
+## v2.20.0 (unreleased)
+
+### Bugs Fixed
+
+* ext/dynblock: if `iterator` is invalid return this error instead of consequential errors. ([#656](https://github.com/hashicorp/hcl/pull/656))
+
## v2.19.0 (October 16, 2023)
### Enhancements
@@ -43,7 +49,7 @@
* 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](https://github.com/hashicorp/hcl/pull/590))
**Note:** This change effectively passes on [`cty`'s notion of backward compatibility](https://github.com/zclconf/go-cty/blob/main/COMPATIBILITY.md) 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](https://github.com/zclconf/go-cty/blob/7dcbae46a6f247e983efb1fa774d2bb68781a333/docs/refinements.md) 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.
## v2.16.2 (March 9, 2023)
@@ -173,7 +179,7 @@
* hclsyntax: Mark objects with keys that are sensitive. ([#440](https://github.com/hashicorp/hcl/pull/440))
## v2.8.1 (December 17, 2020)
-
+
### Bugs Fixed
* hclsyntax: Fix panic when expanding marked function arguments. ([#429](https://github.com/hashicorp/hcl/pull/429))