Skip to content

Conversation

mistydemeo
Copy link

This is configured to look for upstream Mastodon updates, so it isn't actually doing anything useful for Hometown admins. Eventually it can be turned back on if there's a Hometown-specific API that returns the appropriate versions, but in the meantime this feature is misleading.

Looking at the sidekiq-scheduler docs, I think this should be enough to turn it off: https://github.com/sidekiq-scheduler/sidekiq-scheduler?tab=readme-ov-file#schedule-configuration

I also disabled it in the place where upstream Mastodon configures the feature to be on or off: https://docs.joinmastodon.org/admin/upgrading/#automated_checks

Fixes #1367.

This is configured to look for upstream Mastodon updates, so it isn't
actually doing anything useful for Hometown admins.
@dariusk
Copy link

dariusk commented Mar 6, 2025

Thank you this is much appreciated!

@dariusk dariusk merged commit 3b7c5f8 into hometown-fork:v4.2.17+hometown-1.1.1 Mar 6, 2025
16 of 24 checks passed
@mistydemeo mistydemeo deleted the disable-update-checker branch March 6, 2025 16:36
@mistydemeo
Copy link
Author

Thanks for the very fast merge!

@ClearlyClaire
Copy link

Hi! I understand why you disabled this feature, but we've implemented it after noticing people took a long time to update when a security fix is released, and we have observed this feature was pretty effective at making server administrators update.

@mistydemeo
Copy link
Author

The issue is that it's prompting Hometown users to upgrade to versions that don't exist. I'd like to reenable it for Hometown, but that would need a copy of the API service to point to that has relevant data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants