chore: update go dependencies #212

Merged

Wuast94 merged 1 commit from updatarr/go-dependencies-c171078cda into main

2026-09-01 22:02:57 +02:00

Wuast94 commented

2026-09-01 20:01:07 +02:00

Owner

Updates go dependencies.

Automerge: Enabled

Changed files:

go.mod:17 v1.2.1 -> v1.2.3
go.mod:28 v1.16.3 -> v1.19.0
go.mod:30 v0.38.0 -> v0.40.0
go.mod:34 v0.0.0-20231012003039-104605ab7028 -> v0.0.0-20240903120638-7835f813f4da

Release notes

`v1.2.2`: github.com/agext/levenshtein: v1.2.2

Compare source

Enable modules; update CI settings

`v1.2.3`: github.com/agext/levenshtein

Compare source

Fix issue #3

`v1.17.0`: github.com/zclconf/go-cty: v1.17.0

Compare source

cty now requires Go 1.23 or later.

cty.Value.Elements offers a modern iter.Seq2-based equivalent of cty.Value.ElementIterator.
cty.DeepValues offers a modern iter.Seq2-based equivalent of cty.Walk.
cty.Value.WrangleMarksDeep allows inspecting and modifying individual marks throughout a possibly-nested data structure.

Having now got some experience using marks more extensively in some callers, it's become clear that it's often necessary for different subsystems to be able to collaborate using independent marks without upsetting each other's assumptions. Today that tends to be achieved using hand-written transforms either with cty.Transform or cty.Value.UnmarkDeepWithPaths/cty.Value.MarkWithPaths, both of which can be pretty expensive even in the common case where there are no marks present at all.

This new function allows inspecting and transforming marks with far less overhead, by creating new values only for parts of a structure that actually need to change and by reusing (rather than recreating) the "payloads" of the values being modified when we know that only the marks have changed.
cty.ValueMarksOfType and cty.ValueMarksOfTypeDeep make it easier to use type-based rather than value-based mark schemes, where different values of a common type are used to track a specific kind of relationship with multiple external values.
cty.Value.HasMarkDeep provides a "deep" version of the existing cty.Value.HasMark, searching throughout a possibly-nested structure for any values that have the given mark.
cty.Value.UnmarkDeep and cty.Value.UnmarkDeepWithPaths are now implemented in terms of cty.Value.WrangleMarksDeep, so they benefit from its reduced overhead. In particular they avoid reconstructing a data structure that contains no marked values at all.
cty.Value.MarkWithPaths now has a fast path when it's given a zero-length PathValueMarks, in which case it just returns the value it was given with no modifications.

Updates `go dependencies`. Automerge: Enabled Changed files: - `go.mod:17` `v1.2.1` -> `v1.2.3` - `go.mod:28` `v1.16.3` -> `v1.19.0` - `go.mod:30` `v0.38.0` -> `v0.40.0` - `go.mod:34` `v0.0.0-20231012003039-104605ab7028` -> `v0.0.0-20240903120638-7835f813f4da` <details> <summary>Release notes</summary> ### [`v1.2.2`](https://github.com/agext/levenshtein/releases/tag/v1.2.2): github.com/agext/levenshtein: v1.2.2 [Compare source](https://github.com/agext/levenshtein/compare/v1.2.1...v1.2.2) Enable modules; update CI settings ### [`v1.2.3`](https://github.com/agext/levenshtein/releases/tag/v1.2.3): github.com/agext/levenshtein [Compare source](https://github.com/agext/levenshtein/compare/v1.2.1...v1.2.3) Fix issue #3 ### [`v1.17.0`](https://github.com/zclconf/go-cty/releases/tag/v1.17.0): github.com/zclconf/go-cty: v1.17.0 [Compare source](https://github.com/zclconf/go-cty/compare/v1.16.3...v1.17.0) `cty` now requires Go 1.23 or later. - `cty.Value.Elements` offers a modern `iter.Seq2`-based equivalent of `cty.Value.ElementIterator`. - `cty.DeepValues` offers a modern `iter.Seq2`-based equivalent of `cty.Walk`. - `cty.Value.WrangleMarksDeep` allows inspecting and modifying individual marks throughout a possibly-nested data structure. Having now got some experience using marks more extensively in some callers, it's become clear that it's often necessary for different subsystems to be able to collaborate using independent marks without upsetting each other's assumptions. Today that tends to be achieved using hand-written transforms either with `cty.Transform` or `cty.Value.UnmarkDeepWithPaths`/`cty.Value.MarkWithPaths`, both of which can be pretty expensive even in the common case where there are no marks present at all. This new function allows inspecting and transforming marks with far less overhead, by creating new values only for parts of a structure that actually need to change and by reusing (rather than recreating) the "payloads" of the values being modified when we know that only the marks have changed. - `cty.ValueMarksOfType` and `cty.ValueMarksOfTypeDeep` make it easier to use type-based rather than value-based mark schemes, where different values of a common type are used to track a specific kind of relationship with multiple external values. - `cty.Value.HasMarkDeep` provides a "deep" version of the existing `cty.Value.HasMark`, searching throughout a possibly-nested structure for any values that have the given mark. - `cty.Value.UnmarkDeep` and `cty.Value.UnmarkDeepWithPaths` are now implemented in terms of `cty.Value.WrangleMarksDeep`, so they benefit from its reduced overhead. In particular they avoid reconstructing a data structure that contains no marked values at all. - `cty.Value.MarkWithPaths` now has a fast path when it's given a zero-length `PathValueMarks`, in which case it just returns the value it was given with no modifications. </details>

Wuast94 added 1 commit

2026-09-01 20:01:07 +02:00