You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now a new release will release both the subgraph nodes and the subgraph clients. We want to be able to make separate releases for subgraphs (and graph-node) and subgraph clients.
Why
In a situation where the subgraphs don't change but there is a bug fix for a subgraph client, making a new release will trigger also a new build for the graph-node which may cause some deployments to have to update the latest release of the graph-node and re-index when nothing changed in the subgraphs
The text was updated successfully, but these errors were encountered:
What
Right now a new release will release both the subgraph nodes and the subgraph clients. We want to be able to make separate releases for subgraphs (and graph-node) and subgraph clients.
Why
In a situation where the subgraphs don't change but there is a bug fix for a subgraph client, making a new release will trigger also a new build for the graph-node which may cause some deployments to have to update the latest release of the graph-node and re-index when nothing changed in the subgraphs
The text was updated successfully, but these errors were encountered: