cyrgim cda284dac5 Fix schema matching for custom schema files without kind constraints ... When using multiple custom schema locations with direct JSON files, kubeconform incorrectly applied the first schema to all resources. This occurred because schemas without explicit kind constraints (enum/const values) would match any resource type. Added intelligent path-based matching for schemas without kind constraints, allowing proper validation of resources like SecretStore against their intended schemas rather than defaulting to the first available schema. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>		2025-07-18 09:44:05 +02:00
..
cache	Update jsonschema library to v6 (#324)	2025-05-11 02:05:01 +02:00
config	Sanitize csv strings (#258)	2024-05-09 14:21:36 +02:00
loader	Invalid JSON should not be considered an error - see https://github.com/yannh/kubeconform/issues/67 (#327)	2025-05-12 10:21:02 +02:00
output	Fix junit output, also ensure junit output is deterministic (#253)	2023-12-24 18:06:03 +01:00
registry	Add tests for the HTTP loader (#325)	2025-05-11 04:13:07 +02:00
resource	Allow to skip resources using the GVK notation (#92)	2022-10-16 14:59:48 +02:00
validator	Fix schema matching for custom schema files without kind constraints	2025-07-18 09:44:05 +02:00