Skip to content

Fix update logic #61

Description

@FabioRosado

When moving opsdroid-web to v2 I implemented the same logic as we used to have in v1. Although, the logic only works for releases that we do with github. This is because we are hitting a github endpoint to check the latest release.

With opsdroid-desktop, the release was done with GitHub since it is an electron app, but opsdroid-web is released to npm so the endpoint always hits a 404 (because we don't have any release in github).

We should update the logic to check npm instead of Github so the update message works

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingopsdroid-web-v2Issues related to the upcoming version of opsdroid web

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions