Open aciceri opened 7 months ago
included in #15, not to generate unnecessary merges, this is small change
Firstly, not all master commits in cardano-node
pass their CI, so I would rely on releases (maybe we can ask them to create a release branch? because their master is really develop).
Secondly, do we need to support few node versions explicitly? Or is it enough that users can always overwrite cardano-node
input. My opinions is that's enough, let's keep using latest mainnet
.
Firstly, not all master commits in cardano-node pass their CI, so I would rely on releases (maybe we can ask them to create a release branch? because their master is really develop).
Agree :+1:
Secondly, do we need to support few node versions explicitly? Or is it enough that users can always overwrite cardano-node input. My opinions is that's enough, let's keep using latest mainnet.
For now I would target one release and manually update it when needed. If we manually specify a release as our input flake-update
will not update it obviously.
It would be nice targetting multiple versions but we have enough to do for this milestone.
Not directly part of the milestone but it should easy and useful. For now I wouldn't enable
autoMerge
.