Skip to content

fix(deps): update module github.com/santhosh-tekuri/jsonschema/v5 to v6#3

Merged
l4ci merged 1 commit into
mainfrom
renovate/github.com-santhosh-tekuri-jsonschema-v5-6.x
May 6, 2026
Merged

fix(deps): update module github.com/santhosh-tekuri/jsonschema/v5 to v6#3
l4ci merged 1 commit into
mainfrom
renovate/github.com-santhosh-tekuri-jsonschema-v5-6.x

Conversation

@renovate

@renovate renovate Bot commented May 6, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
github.com/santhosh-tekuri/jsonschema/v5 v5.3.1v6.0.2 age confidence

Release Notes

santhosh-tekuri/jsonschema (github.com/santhosh-tekuri/jsonschema/v5)

v6.0.2

Compare Source

v6.0.1

Compare Source

Bug Fixes:

  • fix/schema: field RecursiveRef misspelled
  • fix/schema: missing Deprecated field

check https://redirect.github.com/santhosh-tekuri/jsonschema/discussions/172 to see notes for migrating from v5 to v6

v6.0.0

Compare Source

Improvements

  • mixed dialect support
  • custom $vocabulary support
  • sermver format
  • support for localisation for ValidationError
  • command jv
    • support stdin
    • --insecure and --cacert flag
    • --quiet flag

check https://redirect.github.com/santhosh-tekuri/jsonschema/discussions/172 to see notes for migrating from v5 to v6


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.

@l4ci l4ci merged commit 6e06f52 into main May 6, 2026
1 check passed
@l4ci l4ci deleted the renovate/github.com-santhosh-tekuri-jsonschema-v5-6.x branch May 6, 2026 06:36
l4ci added a commit that referenced this pull request May 6, 2026
…([B18])

Renovate PR #3 merged the jsonschema v5→v6 bump as a no-op `require`
addition without migrating any imports — `go mod tidy` would have
removed the unused v6 line, but the verifier workflow had no gate to
catch it. The same bump in runlog-schema (which does run a tidy gate)
correctly failed CI on this exact pattern. Mirror schema's gate here
and tidy the existing drift in one commit so the new check passes
green on the very first run.
l4ci added a commit that referenced this pull request May 6, 2026
- mirror the gate from runlog-schema generators-smoke into verifier.yml
- drop the unused jsonschema/v6 require that PR #3 left behind
- post-commit `go mod tidy` is a confirmed no-op so the new gate passes green on first run
l4ci added a commit that referenced this pull request May 8, 2026
Each of runUnit, runUnitSubprocess, runIntegration, runReexecute now
calls matchActionPlanNodeTiming on each branch's Assertion against its
captured ExecResult, alongside the existing matchOutcome differential
gate. Reasons accumulate additively before the rejection decision.

Tier sites wired (matched by analogy to the existing matchOutcome calls):
  - unit.go:107 (runUnit, function isolation)
  - unit.go:266 (runUnitSubprocess, subprocess isolation)
  - integration.go:223 (runIntegration, replay mode)
  - reexecute.go:180 (runReexecute, reexecute mode)

mutate.go::classifyOutcome is deliberately NOT wired — mutations
re-run the action under a perturbation and absolute timing thresholds
should not gate them (per F80 plan Approach #3 / Assumption #3).

The check is no-op for any seed whose Assertion fields are zero (all
seeds today except the canonical postgres-update-returning-with-large-
in-list... which declares planning_time_seconds_gt/lt on each branch
and previously had them silently ignored).

Refs M04-F80.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant