[15.0][FIX] upgrade_analysis: new modules cannot be merged/renamed in same version - #3142
Merged
OCA-git-bot merged 2 commits intoDec 31, 2024
Merged
Conversation
Contributor
|
Hi @StefanRijnhart, @legalsylvain, |
This was referenced Dec 12, 2024
Member
|
Thanks for putting the detailed explanation in the PR but can you put in in the commit message as well, and maybe a comment or extra clarification in the docstring? |
…version Issue: v14 has OCA's 10n_eu_oss (https://github.com/OCA/account-fiscal-rule/tree/14.0/l10n_eu_oss), which is renamed in v15 to l10n_eu_oss_oca (https://github.com/OCA/account-fiscal-rule/tree/15.0/l10n_eu_oss_oca) due to new module Odoo's 10n_eu_oss (https://github.com/odoo/odoo/tree/15.0/addons/l10n_eu_oss). Thus, it doesn't makes sense to have in the coverage file the row `|[new] 10n_eu_oss | |Renamed to l10n_eu_oss_oca|`.
MiquelRForgeFlow
force-pushed
the
15.0-fix-upgrade_analysis-minor-things
branch
from
December 31, 2024 17:15
30efad9 to
52545af
Compare
Contributor
Author
|
@StefanRijnhart done |
legalsylvain
approved these changes
Dec 31, 2024
Contributor
|
/ocabot merge patch |
Contributor
|
What a great day to merge this nice PR. Let's do it! |
Contributor
|
Congratulations, your PR was merged at a7bcff7. Thanks a lot for contributing to OCA. ❤️ |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Explanation of first commit: v14 has OCA's
10n_eu_oss(https://github.com/OCA/account-fiscal-rule/tree/14.0/l10n_eu_oss), which is renamed in v15 tol10n_eu_oss_oca(https://github.com/OCA/account-fiscal-rule/tree/15.0/l10n_eu_oss_oca) due to new module Odoo's10n_eu_oss(https://github.com/odoo/odoo/tree/15.0/addons/l10n_eu_oss). Thus, it doesn't makes sense to have in the coverage file the row|[new] 10n_eu_oss | |Renamed to l10n_eu_oss_oca|.Second commit it's obvious, we don't want OU modules appearing in the coverage file.