Add cannon-prestate as prereq to devnet-up

[jyellick]

The devnet-up ultimately requires the cannont-prestate target to have already executed, or the script errors out. Consequently, for someone checking out the repo if they simply do a:

make && make devnet-up

Things still fail. This change simply mirrors a similar check added to the e2e Makefile.

[ajsutton]

Thank you. :)

[ajsutton]

I don't really know how contracts-bedrock-slither didn't get marked as passing - circleci shows it passed fine. @jyellick Can you pull in the latest changes from develop and see if the rebuild gets it sorted please?

Sorry for all the trouble CI seems to cause your PRs...

[jyellick]

Yes, sorry for your cycles spent with the flaking CI as well.

Per your other suggestion to 'unfollow' the project in our Circle instance, unfortunately I don't think that will work, as we want to be able to run CI against changes that either aren't ready or aren't appropriate to upstream.

I am working to get the publish targets going by linking in a GCP instance, but I think there are other caching components of the CI that maybe should be enabled as well? Is there any infra-as-code type repo (or even simple docs) where it's established how to appropriately bootstrap the 3rd party components of the CI config?

[mergify]

This PR has been added to the merge queue, and will be merged soon.

[mergify]

This PR is next in line to be merged, and will be merged as soon as checks pass.

[ajsutton]

Per your other suggestion to 'unfollow' the project in our Circle instance, unfortunately I don't think that will work, as we want to be able to run CI against changes that either aren't ready or aren't appropriate to upstream.

Ah yeah, I was worried that would be the case. It's not a big deal - just means you need to manage rerunning if necessary rather than me.

I am working to get the publish targets going by linking in a GCP instance, but I think there are other caching components of the CI that maybe should be enabled as well? Is there any infra-as-code type repo (or even simple docs) where it's established how to appropriately bootstrap the 3rd party components of the CI config?

No I don't think we've written anything up there, probably worth raising an issue about it so the request is tracked. Most of the CI setup predates me so I'm not too familiar with it either to be honest.