Skip to content

fix(deps): update module github.com/gookit/validate to v1.6.0 - #72

Merged
patrick-hermann-sva merged 2 commits into
mainfrom
renovate/github.com-gookit-validate-1.x
Sep 5, 2026
Merged

fix(deps): update module github.com/gookit/validate to v1.6.0#72
patrick-hermann-sva merged 2 commits into
mainfrom
renovate/github.com-gookit-validate-1.x

Conversation

@renovate

@renovate renovate Bot commented May 27, 2025

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
github.com/gookit/validate v1.5.4v1.6.0 age confidence

Release Notes

gookit/validate (github.com/gookit/validate)

v1.6.0

Compare Source

Internal performance refactor. No public API changes — drop-in upgrade.

Performance
  • Cache per-type reflection metadata (field index, tags, kinds, interface
    checks) in a concurrency-safe type cache; access struct fields via
    FieldByIndex instead of FieldByName.
  • Cache the parsed rule template for "static" struct types (no
    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.
  • Share built-in error messages instead of copying ~150 entries into every
    Translator; resolve with a custom→builtin fallback.
  • Build the built-in context validators (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
  • Fix a stack overflow when building metadata for self-referential or
    mutually-recursive struct types.
  • Fix a data race in Val/Var: concurrent calls shared one validation
    instance and raced on its error/validator maps; each call now uses a
    pooled instance.

v1.5.7

Compare Source

What's Changed

New Contributors

Full Changelog: gookit/validate@v1.5.6...v1.5.7

v1.5.6

Compare Source

Change Log

Fixed
Feature
  • feat: add option to restore request body after reading (#​307) aff7898
Other
  • Add comprehensive GitHub Copilot instructions for gookit/validate (#​306) a96441d
  • ⬆️ dep: upgrade actions and deps to latest version 3dc6a3f
  • 🎨 chore: update some code styles, update git ignore config 0abf62c

What's Changed

New Contributors

Full Changelog: gookit/validate@v1.5.5...v1.5.6

v1.5.5

Compare Source

Change Log

Feature
Other
  • build(deps): bump golangci/golangci-lint-action from 6 to 7 (#​288) 8844616
  • build(deps): bump golangci/golangci-lint-action from 7 to 8 (#​291) 20ea74a
  • 📝 style: modify some code style 8e7eaea
  • 📝 chore: update some code style and some comments 133c917
  • 📝 chore: update some code style and add some testcases 43de360

New Contributors

Full Changelog: gookit/validate@v1.5.4...v1.5.5


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate

renovate Bot commented May 27, 2025

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: docker/go.sum
Command failed: go get -t ./...
go: downloading github.com/gookit/validate v1.6.0
go: downloading github.com/gookit/filter v1.2.3
go: downloading github.com/gookit/goutil v0.7.6
go: dagger/docker imports
	dagger/docker/internal/dagger: package dagger/docker/internal/dagger is not in std (/opt/containerbase/tools/golang/1.26.1/src/dagger/docker/internal/dagger)

@renovate
renovate Bot force-pushed the renovate/github.com-gookit-validate-1.x branch from 352e72e to 0643ba2 Compare August 10, 2025 13:14
@renovate
renovate Bot force-pushed the renovate/github.com-gookit-validate-1.x branch from 0643ba2 to 4f2f4b4 Compare September 6, 2025 08:36
@renovate renovate Bot changed the title fix(deps): update module github.com/gookit/validate to v1.5.5 fix(deps): update module github.com/gookit/validate to v1.5.6 Sep 6, 2025
@renovate
renovate Bot force-pushed the renovate/github.com-gookit-validate-1.x branch 2 times, most recently from 2353870 to 40e72d4 Compare October 11, 2025 12:41
@renovate
renovate Bot force-pushed the renovate/github.com-gookit-validate-1.x branch from 40e72d4 to c3d9515 Compare December 15, 2025 17:02
@renovate
renovate Bot force-pushed the renovate/github.com-gookit-validate-1.x branch from c3d9515 to a2d916c Compare February 2, 2026 21:10
@renovate
renovate Bot force-pushed the renovate/github.com-gookit-validate-1.x branch from a2d916c to 73ead00 Compare February 12, 2026 11:33
@renovate
renovate Bot force-pushed the renovate/github.com-gookit-validate-1.x branch from 73ead00 to e5c29d2 Compare February 24, 2026 17:35
@renovate
renovate Bot force-pushed the renovate/github.com-gookit-validate-1.x branch from e5c29d2 to 2aad50c Compare March 5, 2026 18:36
@renovate
renovate Bot force-pushed the renovate/github.com-gookit-validate-1.x branch from 2aad50c to 5b833ed Compare March 31, 2026 11:12
@renovate renovate Bot changed the title fix(deps): update module github.com/gookit/validate to v1.5.6 fix(deps): update module github.com/gookit/validate to v1.5.7 Mar 31, 2026
@renovate
renovate Bot force-pushed the renovate/github.com-gookit-validate-1.x branch from 5b833ed to 12526c4 Compare March 31, 2026 13:45
@renovate
renovate Bot force-pushed the renovate/github.com-gookit-validate-1.x branch from 12526c4 to d5fb6fa Compare March 31, 2026 15:30
@renovate
renovate Bot force-pushed the renovate/github.com-gookit-validate-1.x branch from d5fb6fa to cad5af5 Compare April 29, 2026 13:38
@renovate
renovate Bot force-pushed the renovate/github.com-gookit-validate-1.x branch from cad5af5 to fbd7100 Compare April 30, 2026 14:37
@renovate
renovate Bot force-pushed the renovate/github.com-gookit-validate-1.x branch from fbd7100 to 693d92a Compare May 12, 2026 09:43
@renovate
renovate Bot force-pushed the renovate/github.com-gookit-validate-1.x branch from 693d92a to cfd1a8a Compare May 18, 2026 11:54
@renovate
renovate Bot force-pushed the renovate/github.com-gookit-validate-1.x branch from cfd1a8a to b7b96bc Compare May 28, 2026 21:13
@renovate
renovate Bot force-pushed the renovate/github.com-gookit-validate-1.x branch from b7b96bc to c937537 Compare June 3, 2026 19:57
@renovate renovate Bot changed the title fix(deps): update module github.com/gookit/validate to v1.5.7 fix(deps): update module github.com/gookit/validate to v1.6.0 Jun 3, 2026
@renovate
renovate Bot force-pushed the renovate/github.com-gookit-validate-1.x branch from c937537 to d7642d1 Compare June 18, 2026 10:20
@renovate
renovate Bot force-pushed the renovate/github.com-gookit-validate-1.x branch from d7642d1 to b39fcce Compare July 12, 2026 09:37
@renovate
renovate Bot force-pushed the renovate/github.com-gookit-validate-1.x branch from b39fcce to 39df9bf Compare August 12, 2026 03:15
@renovate
renovate Bot deployed to linting August 12, 2026 03:16 Active
@renovate
renovate Bot force-pushed the renovate/github.com-gookit-validate-1.x branch from 39df9bf to 0825b42 Compare August 18, 2026 16:47
@renovate
renovate Bot deployed to linting August 18, 2026 16:47 Active
@renovate
renovate Bot force-pushed the renovate/github.com-gookit-validate-1.x branch from 0825b42 to dbbf5ac Compare August 26, 2026 18:34
@renovate
renovate Bot deployed to linting August 26, 2026 18:34 Active
renovate Bot and others added 2 commits September 5, 2026 10:25
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
patrick-hermann-sva force-pushed the renovate/github.com-gookit-validate-1.x branch from dbbf5ac to 98f3560 Compare September 5, 2026 10:27
@renovate

renovate Bot commented Sep 5, 2026

Copy link
Copy Markdown
Contributor Author

Edited/Blocked Notification

Renovate 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.

⚠️ Warning: custom changes will be lost.

@patrick-hermann-sva
patrick-hermann-sva merged commit 7b2e7a1 into main Sep 5, 2026
4 checks passed
@patrick-hermann-sva
patrick-hermann-sva deleted the renovate/github.com-gookit-validate-1.x branch September 5, 2026 10:44
github-actions Bot pushed a commit that referenced this pull request Sep 5, 2026
## [0.128.2](v0.128.1...v0.128.2) (2026-09-05)

### Bug Fixes

* **deps:** update module github.com/gookit/validate to v1.6.0 ([#72](#72)) ([7b2e7a1](7b2e7a1)), closes [#310](#310)
@github-actions

github-actions Bot commented Sep 5, 2026

Copy link
Copy Markdown

🎉 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>
github-actions Bot pushed a commit that referenced this pull request Sep 5, 2026
## [0.128.4](v0.128.3...v0.128.4) (2026-09-05)

### Bug Fixes

* **deps:** bump otel core to v1.46.0, keep the SDK's log pins ([#27](#27)) ([3510388](3510388)), closes [#72](#72) [#306](#306) [#72](#72) [#306](#306)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant