Skip to content

Pin ligo-raven to not be automatically updated if API breaking changes

We anticipate another ligo-raven release in the future that will contain API breaking changes (so will be renamed to 4.0): %ligo-raven 3.3 in lscsoft/raven

We should not automatically update to a version with API breaking changes, but require a full merge request instead.

Edited by Brandon Piotrzkowski

Merge request reports