Migrate the SDK within the core binary
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 225
- Forks
- 19
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 3
Description
Updating the SDK and checking-it in is a hassle, especially since it needs to be updated as the project dependencies change. We should explore integrating it with the regular binary and producing it as an install artifact in the .yarn/ignore/sdks folder.
Contributor guide
No contributing guide indexed for this repository
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
Start by tracing how the core binary is built and how SDKs are currently checked in or produced. Then examine the .yarn/ignore/sdks destination and the regular binary's artifact flow. Done means the SDK is integrated with the binary and produced in that install-artifact location, with dependency updates no longer requiring manual SDK maintenance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100