Add private-testnet-quartzite support#506
Conversation
ab926d9 to
c758eb9
Compare
| github.com/smartcontractkit/chainlink/v2 v2.29.1-cre-beta.0.0.20260618123253-f1ee915b9a56 | ||
| github.com/smartcontractkit/cre-sdk-go v1.12.0 | ||
| github.com/smartcontractkit/cre-sdk-go/capabilities/blockchain/evm v1.0.0-beta.12 | ||
| github.com/smartcontractkit/cre-sdk-go v1.13.0 |
There was a problem hiding this comment.
Ideally it should be but the issue is the chainlink-protos/cre/go dependency which has to be a commit from the capabilities-development branch. We have rules in the repo that requires us to push any changes to the cre package to the cap-dev branch then cherry-pick it to main. Since the 1.14.0 tag is on the commit in main, the commit in cap-dev is on the previous tag which is why this is only updating to 1.13.0 here.
There was a problem hiding this comment.
The reason we have to use a cap-dev commit for chainlink-protos/cre/go is actually because of the chainlink/v2 dependency. Seems like there's some code in core that relies on the cap-dev branch instead of main. So if I try to use a main commit, the CI will break.
No description provided.