This will prevent Postgres “timestamp out of range” errors on peoples’ sites.
Plugins frontend failure looks unrelated?
Do we need a migration to clean up any existing values? IIRC site setting validations are only enforced when the setting is being changed.
There’s not really a danger for these unless they’re actually causing Postgres errors, which should show up in a site’s
/logs. Proactive remediation is probably unnecessary.
This change looks good to me, agree we can just react on errors.
If this history becomes a systemic issue leading to support we can add a migration.