Detect background jobs/migrations that still need to be ran before upgrading
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the “How to upgrade” guidance first, then trace the Updater/upgrade cycle and the background migration checks mentioned in the issue. The work is done when an upgrade detects an environment with unfinished background migrations and consistently refuses the cycle or offers to trigger the jobs, with the chosen behavior documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100