Fix author progress for future releases - #52
Open
digitalgp wants to merge 1 commit into
Open
Conversation
digitalgp
marked this pull request as ready for review
August 16, 2026 13:45
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Author progress currently counts monitored future releases as missing. This keeps an author poster red even when every released monitored title has a file.
This change:
ReleaseDatefrom both the available and required progress counts, while retainingNULLdates for the existing fallback behavior;The issue was reported from an Unraid Docker installation. The fix is intentionally limited to progress statistics and does not change monitoring or future-release visibility.
Fixes #51
Database Migration
NO.
Breaking Changes
None.
How was this tested?
Local Windows test environment, based on the latest
developcommit (2587323):dotnet test src/Chaptarr.Core.Test/Chaptarr.Core.Test.csproj: 2,770 passed, 2 skipped, and 2 unrelated existing failures remained (should_stage_matched_provider_chapters_when_source_duration_matchesand the locale-sensitive decimal assertion inshould_use_scaled_duration_tolerance_for_output_validation).titleSlugvariable inAuthorIndexRow.js; this patch adds no new lint finding.The repository test explicitly verifies the expected
2 / 2released-title progress while the two monitored future titles remain included in the total catalog count (4).Screenshots (UI changes only)
No visual styling is changed. For the Unraid reproduction shown in #51, the red
2 / 3author progress becomes green2 / 2; the future release remains visible and marked as a future release.