fix(deps): update module github.com/gookit/validate to v1.6.0 - #72
Merged
patrick-hermann-sva merged 2 commits intoSep 5, 2026
Merged
Conversation
Contributor
Author
|
renovate
Bot
force-pushed
the
renovate/github.com-gookit-validate-1.x
branch
from
August 10, 2025 13:14
352e72e to
0643ba2
Compare
renovate
Bot
force-pushed
the
renovate/github.com-gookit-validate-1.x
branch
from
September 6, 2025 08:36
0643ba2 to
4f2f4b4
Compare
renovate
Bot
force-pushed
the
renovate/github.com-gookit-validate-1.x
branch
2 times, most recently
from
October 11, 2025 12:41
2353870 to
40e72d4
Compare
renovate
Bot
force-pushed
the
renovate/github.com-gookit-validate-1.x
branch
from
December 15, 2025 17:02
40e72d4 to
c3d9515
Compare
renovate
Bot
force-pushed
the
renovate/github.com-gookit-validate-1.x
branch
from
February 2, 2026 21:10
c3d9515 to
a2d916c
Compare
renovate
Bot
force-pushed
the
renovate/github.com-gookit-validate-1.x
branch
from
February 12, 2026 11:33
a2d916c to
73ead00
Compare
renovate
Bot
force-pushed
the
renovate/github.com-gookit-validate-1.x
branch
from
February 24, 2026 17:35
73ead00 to
e5c29d2
Compare
renovate
Bot
force-pushed
the
renovate/github.com-gookit-validate-1.x
branch
from
March 5, 2026 18:36
e5c29d2 to
2aad50c
Compare
renovate
Bot
force-pushed
the
renovate/github.com-gookit-validate-1.x
branch
from
March 31, 2026 11:12
2aad50c to
5b833ed
Compare
renovate
Bot
force-pushed
the
renovate/github.com-gookit-validate-1.x
branch
from
March 31, 2026 13:45
5b833ed to
12526c4
Compare
renovate
Bot
force-pushed
the
renovate/github.com-gookit-validate-1.x
branch
from
March 31, 2026 15:30
12526c4 to
d5fb6fa
Compare
renovate
Bot
force-pushed
the
renovate/github.com-gookit-validate-1.x
branch
from
April 29, 2026 13:38
d5fb6fa to
cad5af5
Compare
renovate
Bot
force-pushed
the
renovate/github.com-gookit-validate-1.x
branch
from
April 30, 2026 14:37
cad5af5 to
fbd7100
Compare
renovate
Bot
force-pushed
the
renovate/github.com-gookit-validate-1.x
branch
from
May 12, 2026 09:43
fbd7100 to
693d92a
Compare
renovate
Bot
force-pushed
the
renovate/github.com-gookit-validate-1.x
branch
from
May 18, 2026 11:54
693d92a to
cfd1a8a
Compare
renovate
Bot
force-pushed
the
renovate/github.com-gookit-validate-1.x
branch
from
May 28, 2026 21:13
cfd1a8a to
b7b96bc
Compare
renovate
Bot
force-pushed
the
renovate/github.com-gookit-validate-1.x
branch
from
June 3, 2026 19:57
b7b96bc to
c937537
Compare
renovate
Bot
force-pushed
the
renovate/github.com-gookit-validate-1.x
branch
from
June 18, 2026 10:20
c937537 to
d7642d1
Compare
renovate
Bot
force-pushed
the
renovate/github.com-gookit-validate-1.x
branch
from
July 12, 2026 09:37
d7642d1 to
b39fcce
Compare
renovate
Bot
force-pushed
the
renovate/github.com-gookit-validate-1.x
branch
from
August 12, 2026 03:15
b39fcce to
39df9bf
Compare
renovate
Bot
force-pushed
the
renovate/github.com-gookit-validate-1.x
branch
from
August 18, 2026 16:47
39df9bf to
0825b42
Compare
renovate
Bot
force-pushed
the
renovate/github.com-gookit-validate-1.x
branch
from
August 26, 2026 18:34
0825b42 to
dbbf5ac
Compare
Renovate raised the bump in go.mod but its artifacts step failed, so docker/go.sum was never updated and the branch would have landed on main with go.mod and go.sum disagreeing. `dagger functions (docker)` passed anyway because `dagger develop` regenerates go.sum inside the container -- CI green was not evidence the tree was consistent. `go mod tidy` also carries two indirect bumps that are not part of this dependency update: go.opentelemetry.io/otel/sdk/metric v1.41.0 -> v1.43.0 and google.golang.org/grpc v1.79.1 -> v1.79.3. Verified they are pre-existing drift by running tidy against an unmodified main, which produces exactly those two lines and nothing else. Tidy cannot be applied selectively, so they ride along here and main ends up tidy. Verified: go build, go vet and `dagger functions -m ./docker` all pass with validate v1.6.0. This is a same-major bump, unlike the v2 update in #310, which was closed because docker/lint.go imports the v1 path. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01A4HsKKvk5TF1vypsJPqV76
patrick-hermann-sva
force-pushed
the
renovate/github.com-gookit-validate-1.x
branch
from
September 5, 2026 10:27
dbbf5ac to
98f3560
Compare
Contributor
Author
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
patrick-hermann-sva
deleted the
renovate/github.com-gookit-validate-1.x
branch
September 5, 2026 10:44
|
🎉 This PR is included in version 0.128.2 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
patrick-hermann-sva
added a commit
that referenced
this pull request
Sep 5, 2026
Renovate raised the whole opentelemetry-go monorepo, but the PR was broken in
two independent ways.
The reported one: the artifacts step failed, so no go.sum was updated and the
branch would have landed with go.mod and go.sum disagreeing across 28 modules.
`dagger functions` passed anyway, because `dagger develop` regenerates go.sum
inside the container -- CI green was never evidence the committed tree was
consistent.
The second is why this could not simply be rebased. Renovate also raised four
`replace` directives from v0.16.0 to v0.22.0:
replace go.opentelemetry.io/otel/log => go.opentelemetry.io/otel/log v0.22.0
replace go.opentelemetry.io/otel/sdk/log => ... v0.22.0
replace .../otlplog/otlploggrpc => ... v0.22.0
replace .../otlplog/otlploghttp => ... v0.22.0
Those are not stale versions. They are a deliberate pin written by the Dagger
SDK codegen, and github.com/dagger/otel-go v1.43.0 is built against them:
otel-go@v1.43.0/logging.go:47:63: undefined: log.KeyValue
otel-go@v1.43.0/transform.go:872:51: undefined: log.Value
v0.22.0 removed those types, so the bump fails to compile in every module that
imports the generated client -- which is all of them. Renovate cannot
distinguish a deliberate `replace` pin from an outdated dependency.
Isolated the two halves rather than assuming: with the core at v1.46.0 and the
replace directives left at v0.16.0, the tree builds. So the core bump is kept
and the pins are restored.
`renovate.json` now disables updates for those four packages, with the reason
recorded inline, so this PR does not get recreated.
Reapplied on top of #72 and #306 rather than rebased: those two touched the
same `require` blocks in all 28 go.mod files, and resolving 28 conflicts in
generated files by hand is not something to trust. The upstream change is
three direct requires plus four replace lines, so it was reapplied mechanically
and everything else regenerated. Verified gookit/validate v1.6.0 (#72) and
gqlparser v2.5.37 (#306) both survive.
Verified: `go mod tidy`, `go build` and `go vet` pass in all 28 modules.
`dagger functions` spot-checked on kcl, go, ansible, hugo and docker. `dagger
develop` on kcl leaves otel at v1.46.0 and the replaces at v0.16.0, so the fix
survives regeneration.
Note for the govulncheck backlog: grpc stays at v1.79.3 (indirect), so
GO-2026-6061 is not addressed here.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01A4HsKKvk5TF1vypsJPqV76
patrick-hermann-sva
added a commit
that referenced
this pull request
Sep 5, 2026
Renovate raised the whole opentelemetry-go monorepo, but the PR was broken in
two independent ways.
The reported one: the artifacts step failed, so no go.sum was updated and the
branch would have landed with go.mod and go.sum disagreeing across 28 modules.
`dagger functions` passed anyway, because `dagger develop` regenerates go.sum
inside the container -- CI green was never evidence the committed tree was
consistent.
The second is why this could not simply be rebased. Renovate also raised four
`replace` directives from v0.16.0 to v0.22.0:
replace go.opentelemetry.io/otel/log => go.opentelemetry.io/otel/log v0.22.0
replace go.opentelemetry.io/otel/sdk/log => ... v0.22.0
replace .../otlplog/otlploggrpc => ... v0.22.0
replace .../otlplog/otlploghttp => ... v0.22.0
Those are not stale versions. They are a deliberate pin written by the Dagger
SDK codegen, and github.com/dagger/otel-go v1.43.0 is built against them:
otel-go@v1.43.0/logging.go:47:63: undefined: log.KeyValue
otel-go@v1.43.0/transform.go:872:51: undefined: log.Value
v0.22.0 removed those types, so the bump fails to compile in every module that
imports the generated client -- which is all of them. Renovate cannot
distinguish a deliberate `replace` pin from an outdated dependency.
Isolated the two halves rather than assuming: with the core at v1.46.0 and the
replace directives left at v0.16.0, the tree builds. So the core bump is kept
and the pins are restored.
`renovate.json` now disables updates for those four packages, with the reason
recorded inline, so this PR does not get recreated.
Reapplied on top of #72 and #306 rather than rebased: those two touched the
same `require` blocks in all 28 go.mod files, and resolving 28 conflicts in
generated files by hand is not something to trust. The upstream change is
three direct requires plus four replace lines, so it was reapplied mechanically
and everything else regenerated. Verified gookit/validate v1.6.0 (#72) and
gqlparser v2.5.37 (#306) both survive.
Verified: `go mod tidy`, `go build` and `go vet` pass in all 28 modules.
`dagger functions` spot-checked on kcl, go, ansible, hugo and docker. `dagger
develop` on kcl leaves otel at v1.46.0 and the replaces at v0.16.0, so the fix
survives regeneration.
Note for the govulncheck backlog: grpc stays at v1.79.3 (indirect), so
GO-2026-6061 is not addressed here.
Claude-Session: https://claude.ai/code/session_01A4HsKKvk5TF1vypsJPqV76
Co-authored-by: Patrick Hermann <patrick.hermann@sva.de>
Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.5.4→v1.6.0Release Notes
gookit/validate (github.com/gookit/validate)
v1.6.0Compare Source
Internal performance refactor. No public API changes — drop-in upgrade.
Performance
checks) in a concurrency-safe type cache; access struct fields via
FieldByIndexinstead ofFieldByName.ptr-to-struct / slice-of-struct / map-of-struct) and clone it per
validation, skipping the per-instance tag walk and rule parsing. Dynamic
types keep the original per-value path.
Translator; resolve with a custom→builtin fallback.required*,*Field, file checks)lazily on first use instead of eagerly per instance.
Measured (Go 1.25, count=6): static struct validation ~-78% time / -74%
allocations (10403→2295 ns/op, 132→34 allocs/op); map validation -65% /
-42%; slice-of-struct -37% / -20%. Behavior is byte-identical, guarded by a
rule-collection golden test.
Fixes
mutually-recursive struct types.
Val/Var: concurrent calls shared one validationinstance and raced on its error/validator maps; each call now uses a
pooled instance.
v1.5.7Compare Source
What's Changed
New Contributors
Full Changelog: gookit/validate@v1.5.6...v1.5.7
v1.5.6Compare Source
Change Log
Fixed
17116c7306d34374906afdc0ed0c89af7f9Feature
aff7898Other
a96441d3dc6a3f0abf62cWhat's Changed
New Contributors
Full Changelog: gookit/validate@v1.5.5...v1.5.6
v1.5.5Compare Source
Change Log
Feature
dd6d1368f43fe33d8c39a0393362Other
884461620ea74a8e7eaea133c91743de360New Contributors
Full Changelog: gookit/validate@v1.5.4...v1.5.5
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.