- Issue created by @Nigel Cunningham
- Status changed to Fixed
5 months ago 1:16pm 25 June 2024 - πΊπΈUnited States callinmullaney
Thank you @Nigel Cunningham for bringing this to my attention! We had this fixed in 4.9.1 release on our github but wasn't pushed to Drupal. I updated the release and composer should be working for you now.
- π¦πΊAustralia Nigel Cunningham Geelong
Thanks for the reply.
Confirmed that it works now:
$ composer require drupal/emulsify_twig:^5 drupal/emulsify_drupal:^4.9 -W ./composer.json has been updated Running composer update drupal/emulsify_twig drupal/emulsify_drupal --with-all-dependencies Gathering patches for root package. Loading composer repositories with package information Updating dependencies Lock file operations: 0 installs, 2 updates, 0 removals - Upgrading drupal/emulsify_drupal (4.9.0 => 4.9.1) - Upgrading drupal/emulsify_twig (4.0.0 => 5.0.0) Writing lock file Installing dependencies from lock file (including require-dev) Package operations: 0 installs, 2 updates, 0 removals - Downloading drupal/emulsify_drupal (4.9.1) Gathering patches for root package. Gathering patches for dependencies. This might take a minute. - Upgrading drupal/emulsify_twig (4.0.0 => 5.0.0): Extracting archive - Upgrading drupal/emulsify_drupal (4.9.0 => 4.9.1): Extracting archive Generating autoload files 58 packages you are using are looking for funding. Use the `composer fund` command to find out more! No security vulnerability advisories found.
Thanks!
Nij
- Status changed to Fixed
5 months ago 6:56pm 28 June 2024