Skip to content

ci: use a cut-off unit the retention action accepts - #782

Closed
VascoSch92 wants to merge 1 commit into
mainfrom
vasco/fix-ghcr-retention-cutoff
Closed

VascoSch92 wants to merge 1 commit into
mainfrom
vasco/fix-ghcr-retention-cutoff

Conversation

@VascoSch92

Copy link
Copy Markdown
Member

The daily GHCR retention job fails before deleting anything:

error: invalid value '2mo' for '--cut-off <CUT_OFF>': unknown time unit "mo", supported units: ns, us/µs, ms, sec, min, hours, days, weeks, months, years

This switches the default and fallback to 2months and updates the input description examples. Failing run: https://github.com/OpenHands/benchmarks/actions/runs/39539353324

The job is no longer a dry run on schedule, so the first green run will delete eval-agent-server versions older than two months. It still keeps the 100 most recent versions and any v1.0.0* tags.

snok/container-retention-policy v3 rejects 2mo (unknown time unit), so the daily cleanup fails before deleting anything. Use 2months.
@VascoSch92 VascoSch92 closed this Oct 21, 2026
@VascoSch92
VascoSch92 deleted the vasco/fix-ghcr-retention-cutoff branch October 21, 2026 12:01
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.

1 participant