Changelog Organization Best Practice


I have a question around the naming and organization of changelogs

Assume the scenario that I start with a full schema in changelog in the version 1.0.0. I keep on releasing new versions of the database and keep creating the changelogs for those versions at patches

Now once a lot of changelogs have accumulated, I want to consolidate and create a full changelog once again say at version 2.0.0 and then I continue creating further patches

Now I have some customers who are on 1.x version whom I need to upgrade to 2.x version. Now this becomes further complex when after every few releases I consolidate and have a full master once again. How do I create a master/patch changelog strategy to cater to customers who may be in different versions of the product.

Any best practices/experiences are welcome