v3.2.0
Release 3.2.0, available on crates.io
Added
Expression::new_ip
,Expression::new_decimal
,RestrictedExpression::new_ip
,
andRestrictedExpression::new_decimal
(#661, resolving #659)Entities::into_iter
(#713, resolving #680)Entity::into_inner
(#685, resolving #636)- New
ffi
module with an improved FFI interface. This will replace the
frontend
module in the 4.0 release, but is available now for early adopters;
thefrontend
module is now deprecated.
This should be considered a preview-release offfi
; more API breaking
changes are anticipated for Cedar 4.0. (#852) wasm
Cargo feature for targeting Wasm (and thecedar-wasm
crate was added
to this repo).
This should be considered a preview-release ofcedar-wasm
; more API
breaking changes are anticipated for Cedar 4.0. (#858)
Changed
- Common type definitions in both human-readable and JSON schemas may now
reference other common type definitions. There may not be any cycles formed by
these references. (#766, resolving #154) - Improved validation error messages when incompatible types appear in
if
,==
,contains
,containsAll
, andcontainsAny
expressions. (#809, resolving #346) - Deprecated error
TypeErrorKind::ImpossiblePolicy
in favor of warning
ValidationWarningKind::ImpossiblePolicy
so future improvements to Cedar
typing precision will not result in breaking changes. (#716, resolving #539) - Rework API for the
partial-eval
experimental feature (#714, #817, #838). - Validation errors for unknown entity types and action entities now
report the precise source location where the unknown type was encountered.
Error for invalid use of an action now includes a source location containing
the offending policy. (#802, #808, resolving #522) - Deprecated the
frontend
module in favor of the newffi
module. The
frontend
module will be removed fromcedar-policy
in the next major version.
See notes above aboutffi
. (#852) - Deprecated the integration testing harness code. It will be removed from the
cedar-policy
crate in the next major version. (#707)
Fixed
- Validation error message for an invalid attribute access now reports the
correct attribute and entity type when accessing an optional attribute that is
itself an entity. (#811) - The error message returned when parsing an invalid action scope constraint
action == ?action
no longer suggests thataction == [...]
would be a
valid scope constraint. (#818, resolving #563) - Fixed policy formatter reordering some comments around if-then-else and
entity identifier expressions. (#861, resolving #787)
Full Changelog: v3.1.4...v3.2.0