Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unattended migrations of CMS and packages require a restart for the package ones to run #17436

Open
AndyButland opened this issue Nov 6, 2024 · 1 comment
Labels
state/sprint-candidate We're trying to get this in a sprint at HQ in the next few weeks type/bug

Comments

@AndyButland
Copy link
Contributor

AndyButland commented Nov 6, 2024

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

@mattbrailsford
Copy link
Contributor

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.

@bergmania bergmania added the state/sprint-candidate We're trying to get this in a sprint at HQ in the next few weeks label Nov 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state/sprint-candidate We're trying to get this in a sprint at HQ in the next few weeks type/bug
Projects
None yet
Development

No branches or pull requests

3 participants