Have a KNOWN_GOOD_BLOCK_NUMBERS.env that is generated with update-env format.
Setup GH action run every 6 hours, using latest block number, and if all tests passed, update KNOWN_GOOD_BLOCK_NUMBERS.env to the bock number used in tests. Commit and push the change.
Provide a yarn script to update it to the latest value.
When running tests for new PR, loads KNOWN_GOOD_BLOCK_NUMBERS.env. This ensures the PR won't be impacted by new changes in the networks. The RP author can manually bump the block numbers with the provided script if needed.
Have a
KNOWN_GOOD_BLOCK_NUMBERS.env
that is generated withupdate-env
format. Setup GH action run every 6 hours, using latest block number, and if all tests passed, updateKNOWN_GOOD_BLOCK_NUMBERS.env
to the bock number used in tests. Commit and push the change.Provide a yarn script to update it to the latest value.
When running tests for new PR, loads
KNOWN_GOOD_BLOCK_NUMBERS.env
. This ensures the PR won't be impacted by new changes in the networks. The RP author can manually bump the block numbers with the provided script if needed.