Currently one might update a module package while it needs a more recent a2 version!
(Specifically: The never package makes use of a feature in a latest a2 main library. User updates package, a2 is old > a2 breaks on startup)
solution:
When updating a package it checks for the needed a2 version.
problem:
Currently one might update a module package while it needs a more recent a2 version! (Specifically: The never package makes use of a feature in a latest a2 main library. User updates package, a2 is old > a2 breaks on startup)
solution:
When updating a package it checks for the needed a2 version.