Package Champions: Question for you Do we know or can we control the order of PackageMigrationPlans ? As currently they are type scanned and we don't explicitly register them into the CollectionBuilder like other collections AFAIK So I have a package migration that depends on another package - how do I know that their package migration has run BEFORE mine?

I'm just guessing here, but there's probably some collection builder that you can remove and reinsert it with. Could probably find it if you trace the references to package migration plan. The collection builder also determines whether or not it's ordered or weighted by the baseclass that the builder inherits from

Yeh I need to go source code diving...

Hi Warren! The package migrations are indeed type scanned here: https://github.com/umbraco/Umbraco-CMS/blob/0bbda02931e77e5750a66c84ffab870965d2ab30/src/Umbraco.Infrastructure/DependencyInjection/UmbracoBuilder.CoreServices.cs#L80 And added to a lazy collection builder: https://github.com/umbraco/Umbraco-CMS/blob/0bbda02931e77e5750a66c84ffab870965d2ab30/src/Umbraco.Infrastructure/Packaging/PackageMigrationPlanCollectionBuilder.cs#L5 So that means they're not ordered 😢 Changing this to another type will be a breaking change, but it might make sense to either be able to manually order them (

OrderedCollectionBuilderBase

) or add weights (

WeightedCollectionBuilder

): https://docs.umbraco.com/umbraco-cms/implementation/composing#types-of-collections

Shall I raise an issue for this @Ronald Barendse to discuss what options should be

Can't you influence it by addding ComposeAfter attribute on the Composer that triggers the Migration?

you can for 'old school' migrations, because you run them but PackageMigrations are autodiscoved by type and ran in the core, you don't actually get to give an order.

Err I wanted to use PackageMigrations and not old school ones - will raise a PR issue to discuss and see what HQ gang think

This would definitely be something we should discuss (and potentially fix in v13), because it makes sense for certain migrations to run before/after others... So feel free to create a new discussion on the issue tracker @Warren Buckley 👍 Deploy 12 is now also using a package migration to create its database tables, because other packages might use it to create content/schema and Deploy then handles the notifications to write the artifacts to disk and update signatures in the database. Previously we used a custom migration that was executed in a composer, later in the starting notification handler, but both were running after package migrations and therefore too late (ending up in database errors, because the tables don't exist yet on the first startup, which is also most likely when the package migrations are executed)...

One issue for you @Ronald Barendse & @Sebastiaan https://github.com/umbraco/Umbraco-CMS/issues/14813

@Warren Buckley do you know if this got any traction, something we need to do also

Although the following PR is marked as closed, the changes are actually in v13: https://github.com/umbraco/Umbraco-CMS/pull/15138

@Ronald Barendse legend - any idea on where to place this weight?

This should do the trick:

csharp
[Weight(10)]
public class MyMigrationPlan : PackageMigrationPlan