chore: Remove the updates service

Jade commented

2025-04-15 22:34:53 +00:00

Owner

Copying Jason's commit here, authorship has been preserved.

We don't control June's https://pupbrain.dev/check-for-updates/stable endpoint, no guarantee it will stay up. We'll need a replacement at some point

Copying Jason's commit here, authorship has been preserved. We don't control June's `https://pupbrain.dev/check-for-updates/stable` endpoint, no guarantee it will stay up. We'll need a replacement at some point

Jade added 1 commit 2025-04-15 22:34:53 +00:00

chore: Remove the updates service e1302851f2

Signed-off-by: Jason Volk <jason@zemos.net>

Jade force-pushed remove-update-checker from e1302851f2 to 3acc281e57

2025-04-15 22:36:04 +00:00

Compare

Jade commented

2025-04-16 01:54:23 +00:00

Author

Owner

Alternatively replace this with our own endpoint

Aranjedeath commented

2025-04-16 17:10:53 +00:00

Owner

I like the idea of an alert mechanism in-band. This can also be handled in an announcements channel. Or Both, for Maximum Alert.

Jade commented

2025-04-16 17:49:38 +00:00

Author

Owner

I think we can put an endpoint on https://continuwuity.org in the static files of this repository, and just update the endpoint. Perhaps rename it to 'announcements' as it doesn't have any actual version check logic.

Aranjedeath commented

2025-04-16 17:55:47 +00:00

Owner

Yeah that would be great. I think some of the original logic for this was to be a "quick and in-band" way to alert everybody to a security update you may wish to apply. In practice, I think faster+smaller release cadence solves this at least for the container people who have auto-update enabled. But, for others (that have OS packaging considerations/etc) it's maybe still a good idea to have an alert spot.

👍 2