You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)
13+
Bug summary
We've had a couple of reports of people looking to run both a CMS and a package unattended migration at the same time. What's found is that on start-up the CMS migration runs, but the package migration doesn't. When you restart the application, the package migrations run,
Update your CMS and a package's dependency in your .csproj file such that both new versions will require database migrations. Start Umbraco and you will see that only the CMS migrations have run.
Expected result / actual result
Ideally both the CMS and package migrations would run in one step.
This item has been added to our backlog AB#46066
The text was updated successfully, but these errors were encountered:
I can confirm that this is the case. Upgrading CMS and Umbraco Commerce (which depends on Umbraco.Licenses) fails to run the Umbraco.Licenses migrations, but once Umbraco is upgraded and the project is restarted the Umbrac.Licenses migrations run succesfully.
Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)
13+
Bug summary
We've had a couple of reports of people looking to run both a CMS and a package unattended migration at the same time. What's found is that on start-up the CMS migration runs, but the package migration doesn't. When you restart the application, the package migrations run,
Specifics
See this issue on the Forms tracker that discusses the problem.
And specifically this comment where I've detailed a little digging I've done into the problem.
Also this (internal) discussion.
Steps to reproduce
Update your CMS and a package's dependency in your
.csproj
file such that both new versions will require database migrations. Start Umbraco and you will see that only the CMS migrations have run.Expected result / actual result
Ideally both the CMS and package migrations would run in one step.
This item has been added to our backlog AB#46066
The text was updated successfully, but these errors were encountered: