Can Eleventy's incremental build safely roll back after a data‑schema change?

When using Eleventy’s experimental --incremental flag, the build system caches dependencies encountered during template rendering but does not record changes to external JSON or JavaScript data files.

A modification to a data‑source schema therefore may leave previously generated pages unchanged unless a full rebuild is triggered, which raises uncertainty about how to roll back safely after such a change without losing the performance benefits of incremental builds.

What mechanisms or configuration options could be introduced to make the dependency cache aware of data‑file alterations, and how would they interact with existing plugins that modify the data cascade?