2.0.24

New

• A dependency can now name the generation of Grav it is for. A plugin that supports both 1.7 and 2.0 often needs a different version of the same dependency on each, so a dependencies entry takes an optional grav key: - { name: form, version: '>=9.1.0', grav: '2.0' }. Entries without it apply everywhere, so existing blueprints are unchanged. See Plugin Compatibility

Bugfix

• Installing a package whose dependency is not in the GPM index now says so and carries on, instead of stopping the command with a PHP fatal error. A plugin that still asks for the Grav 1.7 admin plugin was enough to trigger it getgrav/grav-premium-issues#618
• A plugin that asks for the admin plugin now has that read as Admin 2 on Grav 2, so a plugin written for both 1.7 and 2.0 installs instead of failing on a dependency that cannot exist there. The version it asks for is not carried over, because it describes the old admin's numbering getgrav/grav-premium-issues#618
• Any other dependency that cannot be installed on this generation of Grav is now left out of the install rather than attempted and failed
• Opening Clockwork before anything has been profiled, on a fresh install or right after bin/grav clear, now reports that there is no data yet instead of failing with a 500