Problem
The cargo-dist Release workflow creates the GitHub release with the workflow GITHUB_TOKEN. GitHub suppresses recursive workflow events created by that token, so docker.yml does not receive its release: published trigger. A public node release can therefore complete without producing the versioned dstack image or deploying Phala. v1.6.0 required a manual workflow_dispatch with image_version=1.6.0 and deploy_phala=true.
Acceptance criteria
- Successful cargo-dist publication durably dispatches
docker.yml for the exact released tag/version.
- The dispatch has only the minimum required permissions and cannot deploy an untagged commit.
- Versioned normal and dstack images are built before deployment.
- Phala deployment failure makes the release/deploy pipeline visibly fail.
- A workflow test or documented dry-run proves the dispatch and version propagation.
- Duplicate release/delivery events are idempotent.
Problem
The cargo-dist Release workflow creates the GitHub release with the workflow GITHUB_TOKEN. GitHub suppresses recursive workflow events created by that token, so
docker.ymldoes not receive itsrelease: publishedtrigger. A public node release can therefore complete without producing the versioned dstack image or deploying Phala. v1.6.0 required a manualworkflow_dispatchwithimage_version=1.6.0anddeploy_phala=true.Acceptance criteria
docker.ymlfor the exact released tag/version.