Explain automatic root snapshot retention in Snapshots settings #22

Merged
Breadway merged 1 commit from feature/bset-20-snapshot-retention into main 2026-10-02 12:22:02 +08:00
Owner

Adds a short note to Settings > Snapshots explaining Snapper's normal and important snapshot ranges, the quota-aware space limits, and that low space can reduce the retained count.

Verification: npm run check and npm run build passed in frontend/.

Closes #21

Adds a short note to Settings > Snapshots explaining Snapper's normal and important snapshot ranges, the quota-aware space limits, and that low space can reduce the retained count. Verification: `npm run check` and `npm run build` passed in `frontend/`. Closes #21
feat: explain Snapper snapshot retention
All checks were successful
check / check (push) Successful in 2m14s
95bbfebc28
Author
Owner

This card duplicates BSET-20: both describe the same Snapshots retention note, and the linked PR #22 is on feature/bset-20-snapshot-retention. The PR is already linked to BSET-20 and remains in review pending the BOS-27 retention change. I’m leaving this duplicate card in backlog rather than creating a second PR or moving it through a duplicate review.

This card duplicates BSET-20: both describe the same Snapshots retention note, and the linked PR #22 is on `feature/bset-20-snapshot-retention`. The PR is already linked to BSET-20 and remains in review pending the BOS-27 retention change. I’m leaving this duplicate card in backlog rather than creating a second PR or moving it through a duplicate review.
Author
Owner

This retention copy depends on BOS-27. BOS-27 and PR #56 are back in TODO because the ten-transaction and space-retention acceptance check has not been run, and BOS main still configures the old limits. Until that implementation lands, this copy would describe behavior BOS does not ship. Returning this item to TODO; re-review after BOS-27 is merged.

This retention copy depends on BOS-27. BOS-27 and PR #56 are back in TODO because the ten-transaction and space-retention acceptance check has not been run, and BOS main still configures the old limits. Until that implementation lands, this copy would describe behavior BOS does not ship. Returning this item to TODO; re-review after BOS-27 is merged.
Author
Owner

Status update: the duplicate BSET-21 card maps to the already-open PR #22 linked to BSET-20. BOS-27 acceptance is now recorded as passed and its issue is in REVIEW, but PR #56 is not in origin/main yet. The settings copy should stay in TODO until that change lands; do not create a second PR.

Status update: the duplicate BSET-21 card maps to the already-open PR #22 linked to BSET-20. BOS-27 acceptance is now recorded as passed and its issue is in REVIEW, but PR #56 is not in `origin/main` yet. The settings copy should stay in TODO until that change lands; do not create a second PR.
Author
Owner

This is a duplicate tracking card for the same existing bos-settings PR #22 already linked to BSET-20. No second implementation or review is needed. Closing the duplicate card; BSET-20 remains in REVIEW with its BOS-27 dependency documented.

This is a duplicate tracking card for the same existing bos-settings PR #22 already linked to BSET-20. No second implementation or review is needed. Closing the duplicate card; BSET-20 remains in REVIEW with its BOS-27 dependency documented.
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Breadway/bos-settings!22
No description provided.