Implement new release monitoring in shanty-watch
#19
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Extend
shanty-watchto periodically check for new releases from monitored artists. When a new release is detected, it should be added to the watchlist as "available" and optionally trigger a notification or automatic download.Release checking — periodically query MusicBrainz (or other configured provider) for each monitored artist's releases. Compare against what's already known in the database. New releases get added to the watchlist with status
available.Scheduling — the check should run on a configurable schedule (e.g., daily, every 12 hours). Use a simple scheduler or cron-like system within the app.
Auto-download option — if enabled, automatically add new releases to the download queue when detected.
Notification hook — when a new release is detected, emit an event that
shanty-notifycan consume (or directly trigger a notification if the notify crate is available).Handling rate limits — if the user monitors hundreds of artists, checking all of them requires many API calls. Spread checks over time to stay within rate limits. Track when each artist was last checked to avoid redundant queries.
Acceptance Criteria
availableDependencies