BreakingHighlight of Weekly #003
Old date filter range attributes rejected in views
start_month, end_month, start_year and end_year on date search filters are now invalid in views. An upgrade script removes them from stored views, but module XML that still sets them fails validation.
On the upgrade checklist: 19.0 → 20.0
Pull requests and commits
Commit message
[REM] base: drop the date filter range attributes from the RNG
start_month, end_month, start_year and end_year stopped being parsed
when the per-view month/year range of `date` search filters was dropped
(odoo/odoo#267980), but they were left in the RNG so that stored
customisations still carrying them would not crash on view validation.
The upgrade script that strips them from stored views is now written
(base/saas~19.5.1.3/end-20-search-date-filters.py), so the escape hatch
is no longer needed: views setting these attributes are cleaned up by
the migration instead of silently validating against a schema that
allows attributes nothing reads anymore.
task-6260555