SpiceDB v1.0 wildcard permissions now require namespace scoping — how should legacy schemas be migrated without silent access changes?
After the v1.0 release, SpiceDB restructured wildcard permission handling: permission: * in a schema is no longer interpreted as a global default and must be scoped explicitly, e.g. permission: <namespace>:* . Schemas written for v0.9.x that still use the legacy pattern can now produce UNKNOWN or DENIED results, or a descriptive ambiguity error, during
spicedb