I'm having an issue on a site that looks like it's broken somehow and thinks it needs to upgrade (from something like cc54g34 -> 12.3.5). I've checked the database and the version looks fine, but can't find what it is comparing to. In v8 days, this used to be stored in the web.config but I can't find where Umbraco finds it in modern versions. Does anyone know where I can find this in v12.3.5 please?

I think it pulls it from the dll, in the bin. I have seen in the past So if you have a site that is at certain version, but a project you are pulling in with a diffrent dependency, the DLLs from the depndenant project overwrite the site ones, and then the versions missmatch.

Cheers Kevin, I thought that might be the case but couldn’t find anything in the code. I’ll check out other project dependencies and see where I get to. The hunt continues 🕵️‍♂️

I think it all comes from here : https://github.com/umbraco/Umbraco-CMS/blob/contrib/src/Umbraco.Core/Configuration/UmbracoVersion.cs

This is usually signal that something either keeps reverting the umbraco migrations table or you deploy a SQLite database with each deploy. It's rare, but I've seen it happen that people commit the SQLite db and don't notice because uSync is so good at reconstructing the site structure/content. Alternatively the upgrade seems to complete but the databae doesn't get the update written to the migrations table.. that should not be possible but.. who knows

I ended up restoring the database to an earlier version, which worked. I checked the KeyValue table for versions as part of my checks and although the Umbraco version was the same there was a bunch of additional items from packages we had. We have Deploy installed which takes an age and a huge amount of memory to run (set on boot). My gut is telling me that this ran, system ran out of memory, and then borked the database mid-migration.

Hmm, should have seen an error I guess but I don't know exactly what happened. Just happy to hear it completed now! I would do a tiny deploy of a change in a template or something to make sure it doesn't want you to upgrade again

We spent a bit more time on it later on and everything seemed fine. This was in dev environment and it happened last week as well, same fix was to restore the database. It’s only happened twice (same dev) and it’s a fairly beefy site. Thanks for helping out ☺️