Clear cache after Directus upgrades

success

This has been fixed in version 3.3.0.

When upgrading Directus, schema-related caches can persist and cause stale metadata (e.g., old FK constraint names).

Directus Sync now clears both the regular cache and, when available in your Directus version/SDK, the system cache at the start of pull, diff, push, and seed commands. This is best-effort; older Directus releases may not expose the system-cache endpoint.

If you still observe stale schema behavior after upgrade, try clearing caches directly in Directus admin (Settings → System → Cache) and re-run the command.

info

Reference: Issue #135