[19.0] initialize+openupgrade_framework #5395
Merged
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
- Apply new copier template. (from v1.14.2 to v1.18 : replace setup by pyproject.toml, replace black by ruff, ...) - Disable .github/workflows/test.yml because the openupgrade is not initialized yet - add new empty modules160-170.rst file
…de is not initialized yet
.github/workflows/test.yml
-This commit remove unecessary patch -Check if test exist then execute it in the test.yml -Remove the test loader from patch, detail at OCA#4327 (comment)
account_peppol by now
Member
Author
|
/ocabot migration openupgrade_framework |
Contributor
|
There's no issue in this repo with the title 'Migration to version 19.0' and the milestone 19.0, so not possible to add the comment. |
Member
Author
|
/ocabot migration openupgrade_framework |
hbrunn
force-pushed
the
19.0-initialize+openupgrade_framework
branch
from
e6a1234 to
21d73b8
Compare
This was referenced Nov 7, 2025
…path does not exist
Member
StefanRijnhart
left a comment
StefanRijnhart
left a comment
There was a problem hiding this comment.
Looking good, but tests fail because of the logged warning and because of the missing 18.0 database in https://github.com/OCA/OpenUpgrade/releases
Member
|
Oh, I see there is #5375. |
Member
Author
|
@StefanRijnhart added a commit that squelches the warning, and given #5375 was merged we have nearly working CI now |
Member
Author
|
i've already cherry picked them back then, so no, i think this is nearly good to go, i'd like to have the openupgrade test skip itself when no modules are marked as migrated though |
hbrunn
force-pushed
the
19.0-initialize+openupgrade_framework
branch
from
4f29cf2 to
9f45f79
Compare
Member
Author
pedrobaeza
approved these changes
Dec 25, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
14 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.
My goal here is to reduce the amount of manual work when dealing with OpenUpgrade.
I proposed a somewhat modified script for branch initialization and following steps, which I used for creating this one.
Note that I renamed the migration test script to test-migration.yml, and keep the standard OCA test script for running unit tests. This should make it easier in future versions to determine which patches we still need, and if they're still effective.
You can see the full thing working on hbrunn#18, but I'm not done yet with the base migration, so no PR for this yet.
Meanwhile for making the migration test work as soon as the base module is migrated, please review #5389 and #5375