Skip to content

Use precise per-drop scheduling - #6

Merged
johnwatso merged 3 commits into
mainfrom
codex/precise-drop-scheduling
Aug 4, 2026
Merged

Use precise per-drop scheduling#6
johnwatso merged 3 commits into
mainfrom
codex/precise-drop-scheduling

Conversation

@johnwatso

Copy link
Copy Markdown
Owner

What changed

SwiftMiner now evaluates each Twitch Drop's own active window alongside its parent campaign before selecting a stream.

  • Future or expired individual rewards no longer make an active campaign eligible for watching.
  • Staggered campaigns remain mineable whenever at least one reward is live.
  • Drops without per-reward dates retain the existing campaign-window behaviour.
  • Subscription-only activity now applies only to currently active rewards.

Why

A campaign can remain visible while its individual rewards have different start and end times. Previously, the campaign window alone could make SwiftMiner look for a stream before the relevant reward opened or after the last reward ended.

Release notes

The 1.36.9 release page now documents precise Drop scheduling, clearer priority and Activity Log behaviour, and the unchanged fallback for campaigns without per-reward dates.

Validation

  • xcodebuild -project SwiftMiner.xcodeproj -scheme SwiftMiner -configuration Debug test
  • xcodebuild -project SwiftMiner.xcodeproj -scheme SwiftMiner -configuration Debug build
  • Built app verified as 1.36.9 (2026080519) with SUFeedURL and SUPublicEDKey present.

Evaluate every Twitch Drop's own active window alongside its parent campaign before selecting a stream.

- Future and expired individual rewards no longer make an active campaign eligible for watching.
- Staggered campaigns remain mineable whenever at least one reward is live.
- Drops without per-reward dates retain the existing campaign-window behaviour.
- Subscription-only activity now applies only to currently active rewards.

Adds model coverage for future, expired, unbounded, and staggered reward windows. Updates the 1.36.9 release notes and build number to 2026080519.
Add emoji-led release-note sections and a dedicated Bug fixes section covering Activity Log clarity, priority-scoped subscription notices, and staggered Drop scheduling. Update the published 1.36.9 build reference to 2026080520.
Present the 1.36.9 Bug fixes section immediately after the release summary, ahead of feature and design improvements. Update the matching build references to 2026080521.
@johnwatso
johnwatso merged commit c1a8f24 into main Aug 4, 2026
1 check passed
@johnwatso
johnwatso deleted the codex/precise-drop-scheduling branch August 4, 2026 23:44
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.

1 participant