Fixed
- Upserting a
CoreNumberPoolwithallow_upsert=Trueno longer raises an error whennodeandnode_attributeare unchanged. (#5636) - Fixed the standard resolver for schema-based objects returning an unhelpful database error when negative values were provided for limit or offset query arguments. (#7474)
- Changing
uniquetoFalseon a schema attribute now correctly triggers a migration that adds the attribute to existing Profile and Template objects. (#8894) - Cardinality constraints (
cardinality: one,min_count,max_count) were silently skipped when the relationship being updated declared its peer as a generic and the constraint was defined on a concrete subtype of that generic, letting data violate the schema. The constraint check and lock path now resolve each peer's concrete kind and enforce the constraint declared there. (#8953)
Full Changelog: infrahub-v1.9.4...infrahub-v1.9.5