Update dependencies

[rmulhol]

No description provided.

[elizabethengelman]

This LGTM. Just curious what the impetus for updating some of these deps is, besides make sure we're have the most recent versions.

I wonder if a similar update needs to made to transformer repos too. 🤔Locally I think I've seen plugin was built with a different version of package... errors if vdb deps don't match up with transformer deps (specifically the geth version).

[elizabethengelman]

💯

[rmulhol]

This LGTM. Just curious what the impetus for updating some of these deps is, besides make sure we're have the most recent versions.

I wonder if a similar update needs to made to transformer repos too. 🤔Locally I think I've seen plugin was built with a different version of package... errors if vdb deps don't match up with transformer deps (specifically the geth version).

Yeah the main impetus is to bring it in line with current transformer repos. Basically trying to sidestep exactly that error while working on a more streamlined deploy

[elizabethengelman]

@rmulhol gotcha! thanks for explanation - I'm running into this sort of issue with storage-diffs-over-rpc right now as well.

I wonder if there's an easier way to keep the deps in these two repos in line 🤔

[rmulhol]

@elizabethengelman I hope so! Thinking it should be possible to say that a versioned release on this repo should be the source of truth for versions of shared dependencies, but not yet sure how to enforce that 🤔

[Gslaughl]