Right now, every update to graphql-import causes two new versions of graphql-cli.
One from graphql-import -> graphql-cli-prepare -> graphql-cli
One from graphql-import -> graphcool-binding -> graphql-cli.
This can be fixed by grouping graphql-import and graphcool-binding together in Renovate.
It's even worse with an update to graphql. This will cause updates of both graphql-import and graphql-static-binding, causing two new versions of graphql-cli-prepare and one new version of graphcool-binding, causing three new versions of graphql-cli.
Right now, every update to
graphql-import
causes two new versions ofgraphql-cli
.One from
graphql-import
->graphql-cli-prepare
->graphql-cli
One fromgraphql-import
->graphcool-binding
->graphql-cli
.This can be fixed by grouping
graphql-import
andgraphcool-binding
together in Renovate.It's even worse with an update to
graphql
. This will cause updates of bothgraphql-import
andgraphql-static-binding
, causing two new versions ofgraphql-cli-prepare
and one new version ofgraphcool-binding
, causing three new versions ofgraphql-cli
.