You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of now, the Release CI action produces some artifacts (runtime WASM and the now deprecated virto-node) and a Docker image that exposes the virto-node.
This process should change to build chain-spec-generator instead and output a Docker image that extends from parity/polkadot-parachain and uses chain-spec-generator to produce the aforementioned chainspec (or store it somewhere in the image).
This is to preserve some degree of compatibility, but it's expected that collators/nodes migrate to a pure implementation of polkadot-parachain.
The text was updated successfully, but these errors were encountered:
As of now, the Release CI action produces some artifacts (runtime WASM and the now deprecated
virto-node
) and a Docker image that exposes thevirto-node
.This process should change to build
chain-spec-generator
instead and output a Docker image that extends fromparity/polkadot-parachain
and useschain-spec-generator
to produce the aforementioned chainspec (or store it somewhere in the image).This is to preserve some degree of compatibility, but it's expected that collators/nodes migrate to a pure implementation of
polkadot-parachain
.The text was updated successfully, but these errors were encountered: