Follow-ups from https://app.notion.com/p/filecoindev/2026-05-28-Hotfix-FWSS-v1-2-0-compatibility-with-PDPVerifier-v3-4-0-901dc41950c1820d99c88157214dec5d?source=copy_link
PDP and FWSS release process have the following improvements:
- Call out if there are any cross-repo changes
- Have calibration and mainnet verification steps for
createDataSet flows. This can either be manually executed or looking at dealbot canary graphs that confirm success.
- Have a section denoting whether a rollback is or isn’t safe. It also links to whatever process/script is devised in PDP and FWSS have a rollback procedure and script.
- Have a step for validating the post-upgrade state in foc-devnet. This will use whatever mechanism is devised in foc-devnet can be executed from CI validating the contract/Curio/Synapse state post contract upgrade.
- Have a named technical owner who helps take the swirl into a written, verified upgrade plan (deployed versions checked against the target, not just intent) and owns the go/no-go.
Follow-ups from https://app.notion.com/p/filecoindev/2026-05-28-Hotfix-FWSS-v1-2-0-compatibility-with-PDPVerifier-v3-4-0-901dc41950c1820d99c88157214dec5d?source=copy_link
PDP and FWSS release process have the following improvements:
createDataSetflows. This can either be manually executed or looking at dealbot canary graphs that confirm success.