fix: Reduce update check interval from 24h to 1h

[charlesvien]

Problem

The 24h update check interval causes users to download a stale update, restart and immediately see another update waiting. The client already re-checks even when an update is staged (periodic checks bypass the updateReady guard), but the 24h window is too long to catch newer versions before the user clicks restart.

NOTE: Since #1938, releases are batched on a 16h cadence instead of shipping on every merge, so it should no longer be the responsibility of the clients to scatter updates and we should actually want to pull the latest updates as soon as possible now because if we push a hotfix we want users to get it sooner than later and we are no longer spammy with our normal commit updates.

Changes

1. Reduce CHECK_INTERVAL_MS from 24 hours to 1 hour
2. Update test to match new interval

How did you test this?

Manually

[charlesvien]

• fix: Downscale large images before attaching #1987
• feat: Show PR and diff status icons on task list items #1986
• fix: Reduce update check interval from 24h to 1h #1985 👈 (View in Graphite)
• fix: Debounce releases and skip empty tags in code workflow #1983
• fix: Fix stacked chevrons in project select dropdowns #1981
• fix: Enrich attachment-only task descriptions for title generation #1980
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[greptile-apps]

_{Reviews (1): Last reviewed commit: "Reduce update check interval from 24h to..." | Re-trigger Greptile}

[jonathanlab]

Good one

[charlesvien]

Merge activity

• May 4, 6:05 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• May 4, 6:30 PM UTC: Graphite rebased this pull request as part of a merge.
• May 4, 6:37 PM UTC: @charlesvien merged this pull request with Graphite.