spinframework / spinframework/spin
CI/e2e: Use canary plugin version when testing template apps
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6.5k
- Forks
- 310
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 24
Description
For template app testing automation (as is done in e2e), when the template requires a plugin (such as templates from the spin-js-sdk and spin-python-sdk repos, js2wasm and py2wasm being the respective plugins), fetch the canary version of the plugin when the template is updated from HEAD of the sdk repo, as is done today. (Unless we set a specific tag/branch, the template is pulled from HEAD due to Spin's cli version being a pre-release when running test automation on main and PR events.)
Depends on the following issues adding canary plugin publishing: https://github.com/fermyon/spin-python-sdk/issues/30 and https://github.com/fermyon/spin-js-sdk/issues/161
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 at the e2e template-app testing automation and trace how templates updated from the SDK repositories select plugin versions. Verify the canary-publishing prerequisites in the linked spin-python-sdk and spin-js-sdk issues, then confirm that HEAD-based template tests use canary plugins while explicitly pinned tags or branches remain unchanged.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100