Repository navigation
chore: upstream dfinity/icp-cli-recipes (motoko) moved to motoko-v5.1.0 #368
Description
dfinity/icp-cli-recipes has moved past the ref the docs are verified against.
Pinned in .sources/upstream.json |
motoko-v5.0.0 |
| Latest release | motoko-v5.1.0 |
| Compare | dfinity/icp-cli-recipes@motoko-v5.0.0...motoko-v5.1.0 |
| Published reference | https://github.com/dfinity/icp-cli-recipes/releases |
What to re-check
Cited in 3 places as the Motoko canister recipe in icp.yaml examples. Each recipe in this repo tags and releases on its own prefix, so it gets its own entry: a single pattern across prefixes would compare rust- against static-site- textually and only ever surface one of them.
How to close this
- Review the changes above against the pages named under "What to re-check".
- Update those pages if anything they state has changed.
- Set
pinnedtomotoko-v5.1.0in.sources/upstream.jsonin the same PR.
If nothing in the docs is affected, bump the pin on its own and say so in the PR.
Procedure: .agents/upstream-tracking.md
Activity
docs: sync content against the ten upstream releases the watcher surf…
marc0olo commentedon Aug 27, 2026
Done in #370. Same additive
visibilitychange; 3 occurrences of@dfinity/motoko@v5.0.0are now@v5.1.0. Pin moved to motoko-v5.1.0.