That would be quite a different matter. The example I gave was:
I'm sure people appreciate that if you want to use the latest features in the Wappler framework or the latest version of Bootstrap etc, you will need to upgrade the site you're working on.
I think the main point of this thread is that the developer should have a choice - do they want the site to stay essentiallly as it or do they want to upgrade? The former may be perfectly sufficient for most purposes (the telephone number or other minor changes, or changes which might involve a little manual coding). The latter may be more appropriate for continued development of the site - it should not be mandatory.
There have been a great many threads where upgrading Wappler has broken something. I think the suggestion proposed in this FR will help prevent this happening, or at least prevent unwelcome surprises. It will give the developer more control and perhaps increase users' confidence in Wappler generally.