Skip to content

Issue-375: apply cleanup timestamp and prefix pruning independently - #376

Closed
TethysSvensson wants to merge 1 commit into
Swatinem:masterfrom
TethysSvensson:tethys/cleanup-fix
Closed

Issue-375: apply cleanup timestamp and prefix pruning independently#376
TethysSvensson wants to merge 1 commit into
Swatinem:masterfrom
TethysSvensson:tethys/cleanup-fix

Conversation

@TethysSvensson

Copy link
Copy Markdown
Contributor

The timestamp branch in rmExcept returned after the first directory entry, so at most one outdated item was ever removed. Replace the early return with continue so every entry is checked.

Decouple the two pruning modes: keepPrefix is now Set | null, where null disables prefix checking, and checkTimestamp independently controls timestamp pruning. The restore path passes null packages to prune purely by timestamp.

Fixes: #375

The timestamp branch in rmExcept returned after the first directory
entry, so at most one outdated item was ever removed. Replace the early
return with continue so every entry is checked.

Decouple the two pruning modes: keepPrefix is now Set<string> | null,
where null disables prefix checking, and checkTimestamp independently
controls timestamp pruning. The restore path passes null packages to
prune purely by timestamp.
@TethysSvensson TethysSvensson changed the title Issue-375: fix: apply cleanup timestamp and prefix pruning independently Issue-375: apply cleanup timestamp and prefix pruning independently Aug 12, 2026
@TethysSvensson TethysSvensson closed this by deleting the head repository Aug 13, 2026
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.

Timestamp cleanup bails after the first entry

1 participant