Version drift: ic-cdk pins (0.19 vs 0.20 vs >= 0.20.1) and the modern-vs-legacy API split
Open
Nobody has claimed this yet.
generated
- Dominant language
- Python
- Stars
- 35
- Forks
- 13
- Avg merge
- 19h 10m
- Merged PRs (30d)
- 22
Description
- Most skills pin
ic-cdk = "0.19": canister-security (:19), vetkd (:129), multi-canister (:374), icrc-ledger (:263), ckbtc (:372), stable-memory (:131), cycles-management (:21), sns-launch (:309). skills/evm-rpc/SKILL.md:131-136pinsic-cdk = "0.20".skills/internet-identity/SKILL.md:323— the attribute flow requiresic-cdk >= 0.20.1.
Not contradictory per se, but combined with the legacy-vs-modern caller/call API split (see the vetkd legacy-API issue), the ecosystem story on which CDK generation to target is inconsistent across skills. Consider aligning on one minimum and one API style.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare the cited skill files, especially skills/evm-rpc/SKILL.md:131-136 and skills/internet-identity/SKILL.md:323, with the other listed ic-cdk pins and the vetkd legacy-API issue. Trace which minimum version and caller/call API style each skill documents. Done means the affected skills present a consistent, agreed CDK-generation story.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100