- First commit to issue fork.
- @jkamizato opened merge request.
- π¬π§United Kingdom Rory Downes
Hi @jkamizato,
I believe that this needs to be merged into the dev branch at least for this module to be used in a D10 site, preferably with a new version tag if appropriate for the branch.This is because it is stopping composer from upgrading to D10 as it still thinks that the module is not D10 compatible.
I have found a way by adding this module's repository separately and refer to the specific fork but that is not something I wish to do if I can help it.
Thanks
Regards Rory
- Status changed to RTBC
8 months ago 2:47pm 16 October 2023 - πΊπΈUnited States rreedy Michigan
I've patched this successfully on my Drupal 9 site, but it fails when I try to upgrade to Drupal 10. I'm at a loss... how am I supposed to continue using this?
- π¨π΄Colombia carma03
@rreddy You should add the fork repository into the
composer.json
file as follows:"repositories": { "drupal": { "type": "composer", "url": "https://packages.drupal.org/8", "exclude": [ "drupal/context_metadata", ] }, "drupal/context_metadata": { "type": "git", "url": "https://git.drupalcode.org/issue/context_metadata-3286759.git" } } . . . "require": { . . . "drupal/context_metadata": "dev-3286759-automated-drupal-10", . . . }
For more instructions, you can visit this documentation Core version compatibility fixes for modules with unmerged changes β