Sometimes in composer-based projects it happens that Drop Guard can't update a module because the update requires to update some other packages. These cases required manually handling via command line before.
We decided to improve this cases and make resolving much easier. If Drop Guard couldn't apply an update for a composer-based project due to any other dependency a "Fix it" button will appear. "Fix" for will be opened by click to this button. Just choose the composer mode (require or update) and specify a list of packages which should be updated and Drop Guard will do it!
This is how it looks like:
Today we released a new update for the Drop Guard module for Drupal 7 which fixes a problem with "user warnings" which was triggered sometimes when our service requested the modules list from users' projects.
The warning looked like:
User warning: The following module is missing from the file system: storage_api. For information about how to fix this, see the documentation page. in _drupal_trigger_error_with_delayed_logging()
This update will automatically be applied for every Drop Guard project where our module is used.
Despite that it's not a security update, Drop Guard will update our module like a security update with a security level provided in your "Update behaviors" settings for every project.
The package webflo/drupal-core-require-dev provides the require-dev dependencies of drupal/core as a standalone package and is used by many developers.
This dependency prevented updating Drupal 8 Core via Drop Guard.
Some requests arrived us to respect that package and now Drop Guard supports the update Drupal 8 Core together with webflo/drupal-core-require-dev.
Now if the webflo/drupal-core-require-dev package is using in your project, Drop Guard will execute update for drupal/core and webflo/drupal-core-require-dev up to the equal versions.
At first we want to thank you Tatár Balázs János (European Commission) and Anja Schirwinski (undpaul) for reporting the issue and discussions about the new feature.
Initially, the development of Drop Guard was done for Drupal 7, which has a sequential version numbering system: 7.10 .. 7.20 .. 7.50. If a user uses 7.50 and 7.51 is available he should apply this update and almost certainly this update will be applied without any problems.
Drupal 8 supports several parallel "active branches", right now it is 8.5, 8.6 and 8.7.
The overview of Drop Guard changes in January:
- Decreased loading time for pages
- Fixed a problem with determining of packages with sub-modules
- Removed the PHP 5.6 executor
... and a lot of other points. Read more in this post.
A tool only performs as good as it’s configured and handled.
This post gives detailed insights into the important touch points of the Drop Guard actions you need to configure in order to benefit from a smooth and individual update pipeline.
It has been a week full of impressions, old and new friends and exciting challenges at Drupal Europe! The Drop Guard team members Joe, Max, Alexey, and Johanna attended the Drupal event from 10th to 14th of September.
This is a brief overview of our Drupal Europe highlights and impressions, enjoy it!
Our CTO Max Madl held his first workshop at Drupal Europe last week. The main goal of this hands-on session was to show the audience what it means to update a Drupal project
b.) with helping tools & services
c.) fully automated.
This post provides you the gateways to the session slides "Drupal Europe 2018: Hackers automate but the Drupal community still downloads modules from drupal.org" and the topics update automation and Auto Update Initiative in Drupal.
I’ve joined the Drupal mentoring team for the first time last week at Drupal Europe.
In this post, I’ll share how and why this contribution changed the way I think about Drupal events and the Drupal Community.