chore(truapi-provider): refresh bundled chain specs - #862
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Automated refresh of the smoldot chain specs bundled in truapi-provider.
This branch is force-pushed on every run, so the newest head can end up with no
checks attached even though earlier ones had them. If none are shown below, push an
empty commit before merging rather than assuming the suite passed.
If
every_catalog_genesis_hash_matches_its_bundled_specfails, a chain has beenre-genesised and its
genesis_hexinrust/crates/truapi-provider/src/networks.rsneeds updating too. The refresh only rewrites the specs, never the catalog constants.
The failure names the network and service, and prints the hash the refreshed spec
derives to on the left and the stale catalog constant on the right. Copy the left one
into
networks.rs, and update any consumer that pins the old hash.Merging this publishes a dev snapshot of
@parity/truapi-providerautomatically(dev-publish.yml triggers on chain-spec changes landing on main). Consumers still
need to bump to the new snapshot to pick up the refresh.