Potential bug: new release might prevent current VM to work
Open
component:cli
component:service
component:setup
type:bug
type:feature
type:integration
type:question
- Dominant language
- Rust
- Stars
- 72
- Forks
- 13
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 5
Description
New releases ship wit new assets -- but the user might have VM using the same profile but older assets. They should still be functional after the update. Potentially need to separate the assets release / checking per profile and allows users to update them indepentely - we already have in theory a status for various assets. Probably need to create a fixed manifest endpoint on capsem site instead of github for those then.
Contributor guide
Assessment
This issue has not been assessed yet.