Skip to content
This repository has been archived by the owner on Oct 2, 2023. It is now read-only.

Implement updating individual apps #51

Open
AaronDewes opened this issue Jul 22, 2022 · 0 comments
Open

Implement updating individual apps #51

AaronDewes opened this issue Jul 22, 2022 · 0 comments

Comments

@AaronDewes
Copy link
Member

Apps should be able to be updatable individually. We already check for updates and can return this ddata from the manager API and expose it in the SDK.

The data will be in this format

{
  "node-red": {
    "updateFrom": "3.0.0",
    "updateTo": "3.0.1"
  },
  "code-server": {
    "updateFrom": "4.5.0",
    "updateTo": "4.5.1"
  },
  "specter-desktop": {
    "updateFrom": "1.10.3",
    "updateTo": "1.10.5",
    "changelog": {
       "1.10.3": "The new things we added in 1.10.3",
       "1.10.4": "The new things we added in 1.10.4",
       "1.10.5": "The new things we added in 1.10.5"
    }
  },
  "oak-node": {
    "updateFrom": "0.3.0",
    "updateTo": "0.3.1"
  }
}

Changelog is optional.

The apps version should be checked by semver, and any changelog entry that is from a later version than the currently installed one should be displayed.

For example, if Specter Desktop can be updated from 1.10.3 to 1.10.5, the changelog for the releases 1.10.4 and 1.10.5 should be displayed, because the user has not yet received these updates.

Please note that this still needs some work on the backend, but the data format is final and is very unlikely to change.

@AaronDewes AaronDewes moved this to 📋 Backlog in Citadel development Jul 22, 2022
@AaronDewes AaronDewes changed the title Implement upating individual apps Implement updating individual apps Jul 22, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
Status: 📋 Backlog
Development

No branches or pull requests

1 participant