spinframework / spinframework/spin
Publish crates to crates.io
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6.5k
- Forks
- 310
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 24
Description
The spin engine and triggers are highly reusuable crates. It will be great to publish them to crates.io so that we can use spin engine as a SDK.
For now there is a workaround:
spin-http-engine = { git = "https://github.com/fermyon/spin", branch = "main" }
spin-loader = { git = "https://github.com/fermyon/spin", branch = "main" }
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
No files or tests are named. Start by locating the package manifests for spin-http-engine and spin-loader and reviewing their crates.io publication requirements. Confirm both crates can be published and consumed as SDK dependencies without the git-based workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100