-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(docs): add manual allowlist check to promote runbook #4034
Conversation
@@ -114,6 +114,8 @@ Modify `DFX_VERSION` in these two files: | |||
|
|||
## Stage 5: Promote the release - day 4 | |||
|
|||
* Precondition: Make sure `dfx deploy --playground` works with a project created by `dfx new`. This makes sure that the asset canister wasm is properly allowlisted in the playground backend. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This means merging the motoko-playground PR first (which is found in the following step, "Merge PRs"). So as written, this precondition can never succeed. We should update this stage to first merge the motoko-playground PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point. I adjusted stage 4 to merge the Motoko playground PR as merging and deploying that PR does not change any public documentation or default behavior
We had it happen multiple times that we promoted a dfx version where
dfx deploy --playground
does not work because the updated allowlist was not deployed in time. With this new check we can make sure this doesn't happen again.