chore(deps): bump cedarpy from 4.12.0 to 4.12.1

[dependabot]

Bumps cedarpy from 4.12.0 to 4.12.1.

Release notes

Sourced from cedarpy's releases.

cedarpy v4.12.1

Patch release on the Cedar 4.12.0 engine line.

Fixed

• is_authorized and is_authorized_batch now say why a request could not be built. A context that Cedar rejects (a JSON null, a float, a record that does not match the action's schema) produced the single diagnostic failed to parse schema from request, which hid the cause and named a schema even when none was passed. The diagnostic is now failed to build request: <cause>, for example failed to build request: while parsing context, found a `null`; JSON `null`s are not allowed in Cedar. Diagnostics for a principal, action, or resource that fails to parse, and for entities that fail to parse, carry their cause the same way (#118). Thanks @​david-long1!

Full Changelog: k9securityio/cedar-py@v4.12.0...v4.12.1

Changelog

Sourced from cedarpy's changelog.

[4.12.1] - 2026-09-23

Fixed

• is_authorized and is_authorized_batch now say why a request could not be built. A context that Cedar rejects (a JSON null, a float, a record that does not match the action's schema) produced the single diagnostic failed to parse schema from request, which hid the cause and named a schema even when none was passed. The diagnostic is now failed to build request: <cause>, for example failed to build request: while parsing context, found a `null`; JSON `null`s are not allowed in Cedar. Diagnostics for a principal, action, or resource that fails to parse, and for entities that fail to parse, carry their cause the same way (#118). Thanks @​david-long1!

Commits

• 1a8a275 Merge pull request #119 from k9securityio/release/4.12.1
• 148ecd0 release: bump version to 4.12.1
• 6c6cdbc Merge pull request #118 from david-long1/fix/request-build-error-chain
• a162ae2 docs: credit @​david-long1 in the CHANGELOG entry for #118
• ac36124 fix: report the cause when an authorization request cannot be built
• dd6861e chore(benchmark): move the regression baseline to v4.12.0
• 3d7b88f test(benchmark): capture v4.12.0 into the historical record
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[imran-siddique]

Dependency update, CI green.