v2.3.2

Release 2.3.2, available on crates.io

What's Changed

Removed

• Move public API for partial evaluation behind experimental feature flag. To
  continue using this feature you must enable the partial-eval feature flag.

Changed

• Improved error detection in schema based parsing (fix issues #73, #74).
  • Detect entities with parents of an incorrect entity type.
  • Detect entities with an undeclared entity type.
• Slightly improved error text on some validation type errors
• Improved error messages for some schema type parsing errors
  • Parsing a schema type without the "type" field will generate an error
    stating that "type" is a required field instead of an inscrutable error
    complaining about the untagged enum SchemaType.
  • Parsing a schema type with a "type" field corresponding to one of the
    builtin types but missing a required field for that type will generate an
    error stating that a required field is missing instead of claiming that it
    could not find "common types" definition for that builtin type.

Full Changelog: v2.3.1...v2.3.2

v2.3.1

Release 2.3.1, available on crates.io

What's Changed

Fixed

• Fix a panic in PolicySet::link() that could occur when the function was called
  with a policy id corresponding to a static policy.

Full Changelog: v2.3.0...v2.3.1

v2.2.2

Release 2.2.2, available on crates.io

What's Changed

Fixed

• Fix a panic in PolicySet::link() that could occur when the function was called
  with a policy id corresponding to a static policy.

v2.3.0

Release 2.3.0, available on crates.io

Changed

Implementation of RFC 9 which disallows embedded whitespace, comments, and control characters in the inputs to several Rust API functions including EntityTypeName::from_str() and EntityNamespace::from_str(), as well as in some fields of the Cedar JSON schema format (e.g., namespace declarations, entity type names), Cedar JSON entities format (e.g., entity type names, extension function names) and the Cedar JSON policy format used by Policy::from_json() (e.g., entity type names, extension function names). The risk that this may be a breaking change for some Cedar users was accepted due to the potential security ramifications; see discussion in the RFC.