-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update drupal/migrate_plus requirement from 6.0.2 to 6.0.4 #3555
Update drupal/migrate_plus requirement from 6.0.2 to 6.0.4 #3555
Conversation
Updates the requirements on drupal/migrate_plus to permit the latest version. --- updated-dependencies: - dependency-name: drupal/migrate_plus dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]>
https://www.drupal.org/project/migrate_plus/releases/6.0.3
|
Looks like this patch release contains a backwards-incompatible API change 😞:
|
…wards-incompatible upstream API change.
Created an issue and MR on drupal.org about the backwards-incompatible changes to the |
There have been some significant changes in this release to the migrate_plus We should also review the classes which override the My testing on this PR also uncovered a seemingly unrelated new issue in 2.11: |
Merged with main to bring in changes from #3558 Verified that:
After the changes @joeparsons made to the function signature of |
A newer version of drupal/migrate_plus exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged. |
https://www.drupal.org/project/migrate_plus/releases/6.0.4 is now available as well. It just includes the fix we contributed for the issue we reported: Fix backwards-incompatible Json data_parser API change included in 6.0.3. @tadean Do you think we ought to consider using 6.0.4 and revert the changes to our plugin class or would you rather keep the changes to match the parent? |
I'm in favor of keeping the changes, since we're overriding the class. I think it makes sense to keep the method matching the parent's signature, even if the 6.0.4 changes make the API change 'opt-in.' |
Retested with |
Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Joe Parsons <[email protected]> Co-authored-by: tadean <[email protected]>
Updates the requirements on drupal/migrate_plus to permit the latest version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)