App won't start after Blazority upgrade due to Alerts changes

[nicolajb23]

Describe the bug
On upgrade from 0.9.4 to 0.12.3 suddenly getting following error

The current thread is not associated with the Dispatcher. Use InvokeAsync() to switch execution to the Dispatcher when triggering rendering or component state.) (The current thread is not associated with the Dispatcher. Use InvokeAsync() to switch execution to the Dispatcher when triggering rendering or component state.)
---> System.InvalidOperationException: The current thread is not associated with the Dispatcher. Use InvokeAsync() to switch execution to the Dispatcher when triggering rendering or component state.
at Microsoft.AspNetCore.Components.Dispatcher.AssertAccess()
at Microsoft.AspNetCore.Components.RenderTree.Renderer.AddToRenderQueue(Int32 componentId, RenderFragment renderFragment)
at Microsoft.AspNetCore.Components.ComponentBase.StateHasChanged()
at Blazority.Internal.AlertsBase.EvalCurrent(Int32 currentIndex)
at Blazority.Internal.AlertsBase.Prev()
at Blazority.Internal.AlertsBase.RemoveAlert(Alert alert)

To Reproduce
Steps to reproduce the behavior:

1. Use in the of the in the main layout of your app

Environment

• Blazority Version [e.g. 22]
• .NET Core Version [e.g. 3.1]
• Browser [e.g. chrome, safari]