fix(deps): update module github.com/santhosh-tekuri/jsonschema/v5 to v6#3
Merged
Merged
Conversation
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.
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:
v5.3.1→v6.0.2Release Notes
santhosh-tekuri/jsonschema (github.com/santhosh-tekuri/jsonschema/v5)
v6.0.2Compare Source
v6.0.1Compare Source
Bug Fixes:
check https://redirect.github.com/santhosh-tekuri/jsonschema/discussions/172 to see notes for migrating from v5 to v6
v6.0.0Compare Source
Improvements
$vocabularysupportsermverformatValidationErrorjv--insecureand--cacertflag--quietflagcheck https://redirect.github.com/santhosh-tekuri/jsonschema/discussions/172 to see notes for migrating from v5 to v6
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.