dfinity/cdk-rs has moved past the ref the docs are verified against.
What to re-check
ic-cdk APIs in Rust code blocks. The repo stopped tagging releases (its newest bare-semver tag is two minors behind the published crate), so the crate version on crates.io is the release identity. Read the sections newer than the pin in https://github.com/dfinity/cdk-rs/blob/master/ic-cdk/CHANGELOG.md, then grep docs/ for the symbols they name. ic-cdk-timers and ic-cdk-executor version separately; check whether they moved too.
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
pinned to 0.20.2 in .sources/upstream.json in 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
dfinity/cdk-rshas moved past the ref the docs are verified against..sources/upstream.json0.20.10.20.2What to re-check
ic-cdkAPIs in Rust code blocks. The repo stopped tagging releases (its newest bare-semver tag is two minors behind the published crate), so the crate version on crates.io is the release identity. Read the sections newer than the pin in https://github.com/dfinity/cdk-rs/blob/master/ic-cdk/CHANGELOG.md, then grep docs/ for the symbols they name.ic-cdk-timersandic-cdk-executorversion separately; check whether they moved too.How to close this
pinnedto0.20.2in.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