Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
On the heels of #2569469: [Policy, no patch] No need to provide an upgrade path for Migrations, we will not be able to get certain tests to pass until migrations are not in the fixtures we use for update path testing. drupal-8.filled.standard.php, at least, contains migrations which need to be removed.
Comment | File | Size | Author |
---|---|---|---|
#7 | 2569605-7.patch | 1.12 MB | phenaproxima |
#5 | 2569605-5.patch | 1.12 MB | phenaproxima |
#2 | 2569605-2.patch | 1.11 MB | phenaproxima |
Comments
Comment #2
phenaproximaRemoved all migrate.migration.* entities from the config table.
Comment #5
phenaproximaPlease gawd...
Comment #6
neclimdulWe should probably empty and leave the update method with a comment.
Comment #7
phenaproximaDone.
Comment #8
neclimdulnon-db changes look straightforward.
Comment #9
phenaproximaCreated a follow-up issue to re-add the migrations once Migrate is stable. #2577801: Re-add migration entities to update path test fixtures when Migrate is stable
Comment #10
webchickGreat, with the creation of that issue I think we can proceed here. This will certainly help us during RC to not have to figure out strange Migrate upgrade path issues (doesn't come up often, but when it does happen it's tricky to work out).
Committed and pushed to 8.0.x. Thanks!