spinframework / spinframework/spin
Plugins on prereleases: compatibility warning and blessed 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 Spin user is on canary or HEAD, and runs a plugin, they see a message warning that they are on a prerelease version of Spin and the plugin may not be compatible.
With cloud moving to a plugin, this warning will now occur on every deployment, which will make the command feel less seamless (again, for the subset of canary users).
Should we:
- Do nothing - retain the warning for all plugins
- Skip the warning for plugins that Spin has special knowledge of (e.g. displays in
spin help, autoinstalls, etc.), because those are meant to feel like part of Spin itself - Drop the warning (or reduce its frequency) for all plugins, because canary users already live in a world of things that may not work right
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, tests, or entry points are named. Start by locating the prerelease warning and plugin invocation handling, then review how the cloud plugin is treated. Done means an agreed policy is implemented for warnings on prerelease versions, including the behavior for blessed and other plugins.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100