I'm trying to get up to speed on this whole issue, after asking to have the corporate wiki I manage updated to a newer version and being informed that the big scary deprecation message appeared and we mustn't upgrade to a version that doesn't support our primary needs. I'm in basically the same situation as @Revansx; I could give more information about my use case if that's needed, but basically we use Cargo and Parser Functions a lot. I hope a solution is possible (and maybe even in progress?) that would allow my wiki to update to a current version without also requiring my whole team of only-moderately-technical folks to learn Lua and then rewrite all of our templates. If there's anything I can do to help make that happen, I'm interested!

I'm also interested in updates on this question. I manage a corporate wiki with a few thousand pages and we don't use Lua or Scribunto. I don't understand what this change will mean for me-- does my team have to rewrite everything that uses ParserFunctions? What support is being offered to help wikis that must make this change? If we have to do a ton of work in order to use a current version, we're going to be in the position Stux describes.

Hello! I see this problem a lot, but on a private corporate wiki so I can't link to examples. It shows up when I'm using cargo queries with format=template (and a variety of templates) and is not a problem with the first save only. The only way to make it stop that I know of is to dummy edit, but sometimes this requires several dummy edits. I'm not using ConfirmEdit or VisualEditor. I'm on MW 1.35.6 with Cargo 3.1