Details
-
Task
-
Resolution: Unresolved
-
Neutral
-
None
-
None
-
None
-
-
Empty show more show less
-
Empty show more show less
Description
We realised when releasing 1.0.6 of the module that it wasn't a reactor. Although that isn't a problem in itself, this was enough to fail our release workflow because every single other module included in bundles actually is a reactor (even if just 1-module reactor). Which is actually a good practice, as per Andrés' TEA session on dependency management.
Rather than add complexity to our release workflow for this module exclusively, we suggest refactoring it into a reactor. This can be done completely transparently.
Checklists
Acceptance criteria