Skip to content

Conversation

@carlos-reynosa
Copy link
Contributor

@carlos-reynosa carlos-reynosa commented Oct 25, 2025

There needs to be a process for detecting when a full upgrade is necessary versus only a db upgrade. The current db:status check is not adequate for detecting when maintenance is needed and in the future to detect when a full upgrade may be necessary.

Currently there does not seem a way to properly detect the need for a full upgrade. For example, changes in RabbitMQ configuration will require a full upgrade and thus the current process does not detect that and deployment failures occur. Magento has not released a way to detect this yet and it is in progress here: magento/magento2#39698

This change will allow for easier maintenance by developers now and in the future when we need to add additional conditions for detecting the need for full upgrades and not only partial db upgrades.

  1. Update main tasks to run general upgrade process that runs either full upgrade or partial db upgrade
  2. Update maintenance check to check for general upgrade needed status
  3. Add full full_upgrade_needed variable will define if a full upgrade is necessary
  • Bug fix #…?

  • New feature?

  • BC breaks?

  • Tests added?

  • Docs added?

    Please, regenerate docs by running next command:
    $ php bin/docgen
    

carlos-reynosa and others added 3 commits October 25, 2025 10:54
There needs to be a process for detecting when a full upgrade is necessary versus only a db upgrade. 

1. Update main tasks to run general upgrade process that  runs either full upgrade or partial db upgrade
2. Update maintenance check to check for general upgrade needed status
3. Add full full_upgrade_needed  variable will define if a full upgrade is necessary
@antonmedv antonmedv merged commit 47a1644 into deployphp:master Oct 26, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants