Back to Signal Feed
CodeTracked since May 14, 2026

Upgrade invopop/jsonschema to v0.14.0 to eliminate a schema-reflection crash

This pull request updates the repository’s `github.com/invopop/jsonschema` dependency from v0.13.0 to v0.14.0, with the primary technical change being a fix that prevents a nil pointer dereference in `ReflectFromType` when handling `ExpandedStruct` during schema generation.

github.com/invopop/jsonschemaReflectFromTypeExpandedStructGo 1.24

What Happened

  • This pull request updates the repository’s `github.com/invopop/jsonschema` dependency from v0.13.0 to v0.14.0, with the primary technical change being a fix that prevents a nil pointer dereference in `ReflectFromType` when handling `ExpandedStruct` during schema generation.
  • This pull request updates the repository’s `github.com/invopop/jsonschema` dependency from v0.13.0 to v0.14.0, with the primary technical change being a fix that prevents a nil pointer dereference in `ReflectFromType` when handling `ExpandedStruct` during schema generation.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

The update imports jsonschema v0.14.0, which specifically adds the guard against nil pointer dereference in `ReflectFromType` for `ExpandedStruct`, reducing crash risk in JSON Schema generation paths.

Why Track This

Why It Matters

Developers using this project for generating JSON Schema from Go structs should see fewer build-time schema-generation crashes for those edge-case types, so CI and tooling runs are less likely to fail unpredictably; teams should continue watching for compatibility impact from the same version bump, especially the new minimum Go 1.24 requirement and any changed behavior in struct tag handling.

Impact

Developers using this project for generating JSON Schema from Go structs should see fewer build-time schema-generation crashes for those edge-case types, so CI and tooling runs are less likely to fail unpredictably; teams should continue watching for compatibility impact from the same version bump, especially the new minimum Go 1.24 requirement and any changed behavior in struct tag handling.

What To Watch Next

  • Watch whether github.com/invopop/jsonschema becomes a repeated pattern.
  • Track follow-up changes around Structured Outputs.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: go_minimum_version_bump, schema_generation_regression.
Open Topic TimelineOpen Technical EventOpen Original Sourcego_minimum_version_bump / schema_generation_regression / dependency_compatibility_review

Supporting Evidence