[FIX] util/modules: trigger autodiscovery outside major upgrade #333
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
|
KangOl
reviewed
Oct 6, 2025
KangOl
reviewed
Oct 6, 2025
Contributor
|
upgradeci retry with always only base |
aj-fuentes
force-pushed
the
master-fix_install_outside_major-afu
branch
2 times, most recently
from
e1faa2e to
3e5ccba
Compare
Outside a major upgrade `base` is already fully loaded. New modules are yet not known for the ORM. We thus need to trigger the discovery. During a major upgrade we also want to block force installing modules outside `base` pre/post. Co-Authored-By: maji@odoo.com Co-Authored-By: chs@odoo.com
aj-fuentes
force-pushed
the
master-fix_install_outside_major-afu
branch
from
3e5ccba to
c12e871
Compare
KangOl
approved these changes
Oct 9, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Outside a major upgrade
baseis already fully loaded. New modules are yet not known for the ORM. We thus need to trigger the discovery.During a major upgrade we also want to block force installing modules outside
basepre/post.