## What this fixes

Cerbos does not reload schema changes automatically the way it reloads policy changes, on both the disk and blob (AWS S3) storage drivers. Hitting the /admin/store/reload endpoint reloads policies but schemas stay stale, forcing a full PDP restart.

## The fix

This was a bug in the store reload path, fixed in Cerbos v0.42.0, upgrade and /admin/store/reload reloads schemas too. If you run a lambda or automation that calls the admin reload endpoint on updates, no config change is needed beyond the upgrade.

Source: https://github.com/cerbos/cerbos/issues/2519

## Why it happens

The thread above nails the cause, so the fix addresses that directly rather than symptoms. Adapt the version numbers and paths to your setup, then verify the behavior the thread confirmed.

## Source

https://github.com/cerbos/cerbos/issues/2519