Overdue not showing up on issues with due in a week

[msdisme]

Not sure of the best way to show this as my test case is in a private repo. . . . . I will create a separate public repo to test it with which I will be able to share. .

[alexleventer]

Fixed in v2.0.0.

Root cause: v1 only added labels — it never removed a stale Due in 1 week label once an issue crossed into overdue, and the Overdue add-path only ran if the transition happened in the same run. If the cron missed the exact window (e.g. the due date passed between two runs, or labels were applied manually), an issue could sit with Due in 1 week forever and never get Overdue.

Fix: the v2 processor reconciles the full managed-label set on every run — any label this action is responsible for that no longer applies is removed, and the correct one is added. It's idempotent, so running it a hundred times in a row produces the same result as running it once. Unmanaged labels (e.g. bug, triage labels) are untouched.

Relevant code + test:

• src/processor.ts — planIssueAction builds the managedLabels set and derives labelsToAdd / labelsToRemove.
• __tests__/processor.test.ts — explicit regression test named "removes stale upcoming label when an issue becomes overdue (issue Overdue not showing up on issues with due in a week #75)".

Please bump your workflow pin to @v2 and the behavior you described should be gone. Thanks for reporting!