There are 7 failing tests, e.g.

Stack Trace:
at FluentMigrator.Tests.Integration.MigrationRunnerTests.<>c.<CanRunMigrations>b__17_1(IServiceProvider serviceProvider, ProcessorBase _) in /home/runner/work/fluentmigrator/fluentmigrator/test/FluentMigrator.Tests/Integration/MigrationRunnerTests.cs:line 514
at FluentMigrator.Tests.Integration.IntegrationTestBase.ExecuteWithProcessor(Type processorType, Action1 initAction, Action2 testAction, Func1 serverOptionsGetter, Boolean tryRollback) in /home/runner/work/fluentmigrator/fluentmigrator/test/FluentMigrator.Tests/Integration/IntegrationTestBase.cs:line 140 at FluentMigrator.Tests.Integration.MigrationRunnerTests.CanRunMigrations(Type processorType, Func1 serverOptions) in /home/runner/work/fluentmigrator/fluentmigrator/test/FluentMigrator.Tests/Integration/MigrationRunnerTests.cs:line 498
at InvokeStub_MigrationRunnerTests.CanRunMigrations(Object, Span`1)
at System.Reflection.MethodBaseInvoker.InvokeWithFewArgs(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)

@jzabroski @PhenX FYI, version 7.2.0 release notes put this PR in the "Code Infrastructure Improvements / Code Style Clean-up" category, when actually this PR is inclusive of the feature itself as well as a few final fixes to tests. I'd suggest moving it to the "Features" category and removing the word "tests" so its more readily understood to be a new feature.

OK, doing that now.