Skip to content

Detect background jobs/migrations that still need to be ran before upgrading #45513

@joshtrichards

Description

@joshtrichards

In our "How to upgrade" docs we say:

Wait for background migrations to finish after major upgrades. After upgrading to a new major version, some migrations are scheduled to run as a background job. If you plan to upgrade directly to another major version (e.g. 24 -> 25 -> 26) you need to make sure these migrations were executed before starting the next upgrade.

We should just check for this ourselves and refuse to trigger an Updater/upgrade cycle if the environment isn't yet compliant. We can either refuse to upgrade - or we could offer to trigger the jobs immediately if desired.

Metadata

Metadata

Assignees

No one assigned

    Projects

    Status

    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions