[v0.32] [DO NOT MERGE] Validate the EpochSetup
parsing is backward-compatible with extra fields
#5013
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ports over service event fixture changes and pins new contract version to validate that
v0.32
is backward-compatible.it turns out that we do not need a patch upgrade on
v0.32
. However, we should still merge this so that[email protected]
uses the same smart contract and service events as will be present on live networks once we deploy onflow/flow-core-contracts#395.TODO
TargetDuration
to Epoch models and API #4987 #5038core-contracts
pin to tagged version, once merged