Artifact retention prune utility for recorded retention-days #1

New issue

Closed

opened 2026-06-16 17:54:53 +00:00 by stephen · 1 comment

stephen commented

2026-06-16 17:54:53 +00:00

Owner

Why

retention-days is recorded in metadata but never enforced by the action. Operators using local storage or buckets without lifecycle rules need a first-party pruning tool.

Verified

README.md says retention-days is recorded but not enforced.
src/lib/upload-impl.js writes retentionDays metadata only.
No existing upload-artifact-action issues are filed.

Build

Add a prune command/script for local and S3 artifact backends.
Read metadata, honor retentionDays, and support dry-run/max-age.
Add tests for missing metadata and active-run preservation.

## Why `retention-days` is recorded in metadata but never enforced by the action. Operators using local storage or buckets without lifecycle rules need a first-party pruning tool. ## Verified - `README.md` says retention-days is recorded but not enforced. - `src/lib/upload-impl.js` writes `retentionDays` metadata only. - No existing upload-artifact-action issues are filed. ## Build - Add a prune command/script for local and S3 artifact backends. - Read metadata, honor retentionDays, and support dry-run/max-age. - Add tests for missing metadata and active-run preservation.

stephen added the

opportunity

labels

2026-06-16 17:54:53 +00:00

stephen referenced this issue from a commit

2026-06-17 00:10:05 +00:00

Add retention prune utility for recorded retention-days (#1)

stephen referenced this issue

2026-06-17 00:10:17 +00:00

Add retention prune utility for recorded retention-days (#1) #2

stephen referenced this issue from a commit

2026-06-17 00:16:00 +00:00

Add retention prune utility for recorded retention-days (#1) (#2)

stephen commented

2026-06-17 18:37:08 +00:00

Author

Owner

Already implemented on main: the retention prune utility shipped in 7276057 (PR #2, merging c9529da). src/prune.js reads each artifact's recorded retentionDays, prunes only entries whose window has elapsed, supports --dry-run and a --force/--max-age fallback for records without a retention window, skips entries with missing/unusable metadata, and preserves fresh runs, with tests. Closing as done; the issue was just never closed at merge time.

Already implemented on `main`: the retention prune utility shipped in `7276057` (PR #2, merging `c9529da`). `src/prune.js` reads each artifact's recorded `retentionDays`, prunes only entries whose window has elapsed, supports `--dry-run` and a `--force`/`--max-age` fallback for records without a retention window, skips entries with missing/unusable metadata, and preserves fresh runs, with tests. Closing as done; the issue was just never closed at merge time.

stephen closed this issue

2026-06-17 18:37:08 +00:00