forked fromANT0071/coder
- Notifications
You must be signed in to change notification settings - Fork0
Commit2e06b6f
authored
chore: bump github.com/zclconf/go-cty from 1.16.3 to 1.17.0 (coder#19735)
Bumps [github.com/zclconf/go-cty](https://github.com/zclconf/go-cty)from 1.16.3 to 1.17.0.<details><summary>Release notes</summary><p><em>Sourced from <ahref="https://github.com/zclconf/go-cty/releases">github.com/zclconf/go-cty'sreleases</a>.</em></p><blockquote><h2>v1.17.0</h2><p><code>cty</code> now requires Go 1.23 or later.</p><ul><li><p><code>cty.Value.Elements</code> offers a modern<code>iter.Seq2</code>-based equivalent of<code>cty.Value.ElementIterator</code>.</p></li><li><p><code>cty.DeepValues</code> offers a modern<code>iter.Seq2</code>-based equivalent of <code>cty.Walk</code>.</p></li><li><p><code>cty.Value.WrangleMarksDeep</code> allows inspecting andmodifying individual marks throughout a possibly-nested datastructure.</p><p>Having now got some experience using marks more extensively in somecallers, it's become clear that it's often necessary for differentsubsystems to be able to collaborate using independent marks withoutupsetting each other's assumptions. Today that tends to be achievedusing hand-written transforms either with <code>cty.Transform</code> or<code>cty.Value.UnmarkDeepWithPaths</code>/<code>cty.Value.MarkWithPaths</code>,both of which can be pretty expensive even in the common case wherethere are no marks present at all.</p><p>This new function allows inspecting and transforming marks with farless overhead, by creating new values only for parts of a structure thatactually need to change and by reusing (rather than recreating) the"payloads" of the values being modified when we know that onlythe marks have changed.</p></li><li><p><code>cty.ValueMarksOfType</code> and<code>cty.ValueMarksOfTypeDeep</code> make it easier to use type-basedrather than value-based mark schemes, where different values of a commontype are used to track a specific kind of relationship with multipleexternal values.</p></li><li><p><code>cty.Value.HasMarkDeep</code> provides a "deep"version of the existing <code>cty.Value.HasMark</code>, searchingthroughout a possibly-nested structure for any values that have thegiven mark.</p></li><li><p><code>cty.Value.UnmarkDeep</code> and<code>cty.Value.UnmarkDeepWithPaths</code> are now implemented in termsof <code>cty.Value.WrangleMarksDeep</code>, so they benefit from itsreduced overhead. In particular they avoid reconstructing a datastructure that contains no marked values at all.</p></li><li><p><code>cty.Value.MarkWithPaths</code> now has a fast path when it'sgiven a zero-length <code>PathValueMarks</code>, in which case it justreturns the value it was given with no modifications.</p></li></ul></blockquote></details><details><summary>Changelog</summary><p><em>Sourced from <ahref="https://github.com/zclconf/go-cty/blob/main/CHANGELOG.md">github.com/zclconf/go-cty'schangelog</a>.</em></p><blockquote><h1>1.17.0 (September 5, 2025)</h1><p><code>cty</code> now requires Go 1.23 or later.</p><ul><li><p><code>cty.Value.Elements</code> offers a modern<code>iter.Seq2</code>-based equivalent of<code>cty.Value.ElementIterator</code>.</p></li><li><p><code>cty.DeepValues</code> offers a modern<code>iter.Seq2</code>-based equivalent of <code>cty.Walk</code>.</p></li><li><p><code>cty.Value.WrangleMarksDeep</code> allows inspecting andmodifying individual marks throughout a possibly-nested datastructure.</p><p>Having now got some experience using marks more extensively in somecallers, it's become clear that it's often necessary for differentsubsystems to be able to collaborate using independent marks withoutupsetting each other's assumptions. Today that tends to be achievedusing hand-written transforms either with <code>cty.Transform</code> or<code>cty.Value.UnmarkDeepWithPaths</code>/<code>cty.Value.MarkWithPaths</code>,both of which can be pretty expensive even in the common case wherethere are no marks present at all.</p><p>This new function allows inspecting and transforming marks with farless overhead, by creating new values only for parts of a structure thatactually need to change and by reusing (rather than recreating) the"payloads" of the values being modified when we know that onlythe marks have changed.</p></li><li><p><code>cty.ValueMarksOfType</code> and<code>cty.ValueMarksOfTypeDeep</code> make it easier to use type-basedrather than value-based mark schemes, where different values of a commontype are used to track a specific kind of relationship with multipleexternal values.</p></li><li><p><code>cty.Value.HasMarkDeep</code> provides a "deep"version of the existing <code>cty.Value.HasMark</code>, searchingthroughout a possibly-nested structure for any values that have thegiven mark.</p></li><li><p><code>cty.Value.UnmarkDeep</code> and<code>cty.Value.UnmarkDeepWithPaths</code> are now implemented in termsof <code>cty.Value.WrangleMarksDeep</code>, so they benefit from itsreduced overhead. In particular they avoid reconstructing a datastructure that contains no marked values at all.</p></li><li><p><code>cty.Value.MarkWithPaths</code> now has a fast path when it'sgiven a zero-length <code>PathValueMarks</code>, in which case it justreturns the value it was given with no modifications.</p></li></ul><h1>1.16.4 (August 20, 2025)</h1><ul><li><code>cty.UnknownAsNull</code> now accepts marked values andpreserves the given marks in its result. Previously it had no directsupport for marks and so would either panic or return incorrect resultswhen given marked values.</li></ul></blockquote></details><details><summary>Commits</summary><ul><li><ahref="https://github.com/zclconf/go-cty/commit/da4c600729aefcf628d6b042ee439e6927d1104e"><code>da4c600</code></a>CHANGELOG: Prepare for v1.17.0 release</li><li><ahref="https://github.com/zclconf/go-cty/commit/b13ddd40b1cd39b19c1acfab789049d7ff34358c"><code>b13ddd4</code></a>cty: Use WrangleMarksDeep for UnmarkDeep and UnmarkDeepWithPaths</li><li><ahref="https://github.com/zclconf/go-cty/commit/4453ac2b7f5200601370c6a3f27207ebc81d2df4"><code>4453ac2</code></a>cty: Use DeepValues instead of Walk for deep marks inspections</li><li><ahref="https://github.com/zclconf/go-cty/commit/f833b10b8efd62c42155b93ab1864c77c836dbc0"><code>f833b10</code></a>Bulk replace interface{} -> any</li><li><ahref="https://github.com/zclconf/go-cty/commit/d4bb9d4fb66471b4ffd521770f5a9f4ff277ee04"><code>d4bb9d4</code></a>cty: Various new mark-inspecting helpers</li><li><ahref="https://github.com/zclconf/go-cty/commit/31572cfc28dc2446e7f163451f78116c6cf776bb"><code>31572cf</code></a>cty+ctymarks: Deep mark wrangling helper</li><li><ahref="https://github.com/zclconf/go-cty/commit/d95a68cf6be26d4d0c841a6de102483c9d382006"><code>d95a68c</code></a>cty: Modern iter.Seq2 equivalents of Value.ElementIterator and Walk</li><li><ahref="https://github.com/zclconf/go-cty/commit/e76eeea526f53bec67a8fda74d68c9593f1a500a"><code>e76eeea</code></a>v1.16.4 release</li><li><ahref="https://github.com/zclconf/go-cty/commit/700a2bccfebdc72ce9270b9715dd2d4e86bd1fa6"><code>700a2bc</code></a>cty: UnknownAsNull accepts marked values and preserves marks</li><li><ahref="https://github.com/zclconf/go-cty/commit/3c2b6a0e21d8e541c2ff5b3825b27483fad0bd1b"><code>3c2b6a0</code></a>Prepare for future v1.16.4 release</li><li>See full diff in <ahref="https://github.com/zclconf/go-cty/compare/v1.16.3...v1.17.0">compareview</a></li></ul></details><br />[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)Dependabot will resolve any conflicts with this PR as long as you don'talter it yourself. You can also trigger a rebase manually by commenting`@dependabot rebase`.[//]: # (dependabot-automerge-start)[//]: # (dependabot-automerge-end)---<details><summary>Dependabot commands and options</summary><br />You can trigger Dependabot actions by commenting on this PR:- `@dependabot rebase` will rebase this PR- `@dependabot recreate` will recreate this PR, overwriting any editsthat 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 afteryour CI passes on it- `@dependabot cancel merge` will cancel a previously requested mergeand block automerging- `@dependabot reopen` will reopen this PR if it is closed- `@dependabot close` will close this PR and stop Dependabot recreatingit. You can achieve the same result by closing it manually- `@dependabot show <dependency name> ignore conditions` will show allof the ignore conditions of the specified dependency- `@dependabot ignore this major version` will close this PR and stopDependabot creating any more for this major version (unless you reopenthe PR or upgrade to it yourself)- `@dependabot ignore this minor version` will close this PR and stopDependabot creating any more for this minor version (unless you reopenthe PR or upgrade to it yourself)- `@dependabot ignore this dependency` will close this PR and stopDependabot creating any more for this dependency (unless you reopen thePR or upgrade to it yourself)</details>Signed-off-by: dependabot[bot] <support@github.com>Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>1 parentd59a4c5 commit2e06b6f
2 files changed
+3
-3
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
433 | 433 | | |
434 | 434 | | |
435 | 435 | | |
436 | | - | |
| 436 | + | |
437 | 437 | | |
438 | 438 | | |
439 | 439 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1908 | 1908 | | |
1909 | 1909 | | |
1910 | 1910 | | |
1911 | | - | |
1912 | | - | |
| 1911 | + | |
| 1912 | + | |
1913 | 1913 | | |
1914 | 1914 | | |
1915 | 1915 | | |
| |||
0 commit comments
Comments
(0)