You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be really great if there was an additional step to aegir release that accepted a list of module names from config, generated a table of the currently installed versions of those modules and appended that information to the GitHub release notes that were just created.
This would let us have an automated compatibility matrix for libp2p releases. So we can say that [email protected] is compatible with @chainsafe/[email protected] for example.
The text was updated successfully, but these errors were encountered:
It would be really great if there was an additional step to
aegir release
that accepted a list of module names from config, generated a table of the currently installed versions of those modules and appended that information to the GitHub release notes that were just created.This would let us have an automated compatibility matrix for libp2p releases. So we can say that
[email protected]
is compatible with@chainsafe/[email protected]
for example.The text was updated successfully, but these errors were encountered: