Closed xStrom closed 1 year ago
The previous strict dependency specification was because cargo was giving us unexpected versions when 0.5.0-pre1 type of versions were at play.
0.5.0-pre1
That isn't the case with the 0.6.0 line. Thus it makes sense to relax the specification, so that a potential 0.6.1 will reach Druid automatically.
0.6.0
0.6.1
The previous strict dependency specification was because cargo was giving us unexpected versions when
0.5.0-pre1type of versions were at play.That isn't the case with the
0.6.0line. Thus it makes sense to relax the specification, so that a potential0.6.1will reach Druid automatically.