ForeignKey setup clarification on updating related fields
You could solve this with a two-column foreign key and cascading update, but that requires a redundant two-column unique constraint on report, which will harm DML performance and use extra storage space.
The proper solution is to remove the redundant column from report_years. This concept of removing redundancy from a data model to improve consistency is so important that there is a name for it: normalization.