The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Problem/Motivation
The Patch from https://www.drupal.org/project/ds/issues/2975313 is preventing updates. Guess it's allready applied right now
Steps to reproduce
Try to Update 4.1 via composer
Proposed resolution
remove patch
Remaining tasks
change composer.json in profile
User interface changes
none
API changes
none
Data model changes
none
Additional info:
I managed to update vardoc manually by changing the stoppeng-on-patch-failuere from true to false. in composer.json as well as in ../profiles/vardoc/composer.json. In fact Vardoc 4.1 is currently not installable anymore without doing that change, because composer will break the process after downloading the vardoc profile and will not download the rest of the files needed.
Comments
Comment #2
joachim namysloComment #3
tseven commentedI've run into this issue as well.
Joachim,
Can you provide more details on how you got around this? How did you update Vardoc manually?
Thanks
Comment #4
joachim namysloThe easiest way to do is to edit composer. Json and change exit on patch failure from true to false.
It's on the bottom of composer.json.
That is not a recommended workaround, because if there will be an update patch as may not checked against failures via composer. But if you track this issue you can reset the switch once this issue is updated and fixed by vardot.
There are several modules within the distribution not updated currently. That's because they focus on Varbase and Drupal 9 right now.
As soon as there is a stable 9 release of Varbase there may be some time to fix and update vardoc. This is just an educated guess and nothing official.
Comment #5
rajab natshahComment #7
rajab natshahThanks, Joachim for reporting.
Committed ... Thank you :)
This will be in the 4.0.x and 5.0.x branches.
Comment #8
rajab natshahComment #9
rajab natshahComment #10
rajab natshah