Dependencies of modules: New quick fix feature

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:


New release for Drop Guard module

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.

Update Drupal 8 Core with dev modules

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.

Improved behavior for update Drupal 8 Core

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.