Open multun opened 6 months ago
Currently, builds of core aren't quite reproducible: if a new version of a dependency is published that matches our version specification, it may cause the build or runtime to fail without notice, nor easy way to understand what happened.
We should instead:
A list of conditions which define when this task shall be considered complete
This is dependabot's gradle lockfile issue: https://github.com/dependabot/dependabot-core/issues/2222
Description and goal
Currently, builds of core aren't quite reproducible: if a new version of a dependency is published that matches our version specification, it may cause the build or runtime to fail without notice, nor easy way to understand what happened.
We should instead:
Acceptance criteria
A list of conditions which define when this task shall be considered complete