spinframework / spinframework/spin
Ability to release a canary release of Spin, with corresponding templates, SDKs, and plugins.
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6.5k
- Forks
- 310
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 24
Description
If a user wants to try canary Spin, which includes new SDK, template or plugin features, it's not a straight forward process to get in alignment with what's supported, and a default setup.
The install script is trying to solve some of this through the canary flag, but there might be things in templates and plugins as well to consider.
This issue is meant to identify the work across the suite, to make this an easier experience.
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
Start with the install script and its canary flag, then inventory the templates, SDKs, and plugins that must align with a canary Spin release. Map the suite-wide changes needed so users receive a consistent supported setup, and define completion as a documented, working canary path across those components.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, wasm
- Domain
- release, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100