feat: check for new releases (ActivityWatch/activitywatch#114)

[billangli]

Web UI Changes

I added the following alerts to the top of the webpages. The following shows if there is a new update.

After clicking disable, the follow up tells the user that they can re-enable the check.

The following is where you can change the settings.

All of the above components will not be rendered if the web app is built using npm run build -- --os=android instead of just npm run build. See ActivityWatch/aw-android#50.

When does it check?

Let's define checking by getting the release versions from the /info endpoint and the GitHub API and displying the notification if there is a different version.

Every time the web app is loaded (e.g. on a refresh or close and then reopen tab), it will perform check if the backoff period ends. The backoff period is usually 1 day. After 5 consecutive notifications reminding the user to download the update, it will change the backoff period to 5 days.

Notes

• Future release tag names should follow the Semantic Versioning Specification, for example, v0.8.0b9 should be changed to v0.8.0-beta.9, because this component uses the semver package
• I also moved src/util/classes.test.js → test/unit/classes.test.node.js to fit in with the rest of the tests, it runs sucessfully
• screenshot.test.js is ignored when running npm test (because it wasn't run before, but now it's getting picked up by my changes in jest.config.js)

Fixes ActivityWatch/activitywatch#114

[ErikBjare]

Very nice work!

I haven't reviewed super carefully but overall very happy with the changes :)

[billangli]

Great! Thanks for the words of encouragement, I'll make the changes soon 👍

[ErikBjare]

One question regarding the jest config, but I'm overall very happy with these changes, so I'll go ahead and merge :)

[ErikBjare]

Will this work for tests written in TypeScript?

[ErikBjare]

Thanks a lot for the contribution! 🎉

This is a huge improvement. Making sure ActivityWatch is kept up-to-date is important for so many reasons (just to pick a few: no bug reports for old versions, improved user retention/engagement, a step towards becoming "evergreen" software).

[billangli]

Thanks @ErikBjare! I am glad to help with this useful project. If you have any coding-related work that needs help with, feel free to let me know. I'd be happy to try my hand on it.

I've looked at the rest of the issues in the to-do list of Road to 1.0 and these three seem like they haven't been visited in a while:

• Remaining tasks after categorization PR #151
• Doesn't shut down properly aw-qt#49
• Category name edit, also affects sister category activitywatch#361

If you don't need a hand with these I can always dig up other issues to work on.

[ErikBjare]

@billangli Missed your comment, sorry! #151 looks a bit messy/unclear, but would love to see you work on the others!

[billangli]

@ErikBjare great! Thanks for letting me know