breaking changes after "upgrade" - problems with "run --local"?

I just realized a strange behaviour - let's assume the problem is sitting in front of the desktop ...

nevertheless, maybe someone else has the same issue. What happened? I just upgraded npm packages and aio to latest versions and tried the "aio app run --local" as usual. What I see looks as if there is some deployment similar to "aio app deploy" for some of the files, especially the "manifest.yml". not only takes it a lot longer to build my local files, it also looks quite different than before. did something change in the build process?

But the most confusing part: I had an app up and running in the same environment (I used "aio app deploy" before) with a schedule to run every hour. after the uprade the hourly scheduled stopped working ... I checked the "aio runtime activation list" without seeing any error. I assume that the last "aio app run -- local" uploaded the manifest.yml and stopped the trigger ...

happy to provide more information and get response if somebody has similar issues...