1c5cf42d00
- Used a random post-Shanghai-created USV2 pool state with enough liquidity for the test Necessary fixes: - Don't hardcode to EVMPoolState - Don't expect adapter to always be set. - UniswapV2 names its module differently for some reason... this seems like a special case so instead of updating all integration test yamls, I'm just hardcoding it in test_runner.rs. Perhaps not the best decision? - Log the static attributes if not found. - Get the substreams yaml path from config instead of hardcoding it.
Substreams Indexing Integrations
Please refer to the official Substreams Indexing docs.
Release
To release a package simply tag a commit with the package name and its version:
e.g. ethereum-balancer-0.1.0. This will create a release and automatically build
and push the spkg into our registry.
Note
The CD pipeline will error if the Cargo version is not the same as the version in the tag.
Releases are immutable so do not try to delete tags or build the same release twice since this will error.
Pre-release
To create a pre-release for testing in dev you can start CD pipeline manually supplying
the package you'd like to pre-release. This will create a
[package].pre-[commit-sha] release in our spkg repository which you can use
to run the substream.
For forked protocols you'll need to also supply the config file name, e.g. ethereum-pancakeswap.
Test your implementation
To run a full end-to-end integration test you can refer to the testing script documentation.