So I’ve started using the Umbraco Extension and followed the tutorial linked above. I’m using this with a project that we’re updating from v13 to v17. We started this when 17.1.0 was out and used this to update our Umbraco backoffice.
Everything was fine until suddenly we started getting errors from our database and couldn’t log in as we we’re being prompted with an upgrade message. It turned out that our 17.1.0 database had been updated to 17.2.0 even though none of the development team had updated to 17.2.0! After some digging around we noticed that the Umbraco Extentions project has its dependencies for Umbraco set to * rather than a specific number. I can only assume the reason for this is so that no matter when someone is using the extension’s template, it will work with the latest version of Umbraco. However, the problem with this is that when someone builds their project either locally or via a deployment, it’s going to download the latest version as instructed by the Extensions project and when Umbraco runs, it’s going to update the db to the latest version.
Is this intended? Not evey project is going to be immediately updated to the latest and greatest version of Umbraco when it comes out! The linked tutorial doesn’t seem to warn that this could happen and you’re not prompted to specify a version when running the dotnet set up. You can however set a version if you add it via Visual Studio. Seem to me that having the dotnet run like this seems a risky approach that could inadvertedly start upgrading instances when not required?