Keep N most recent AND keep all younger than X days/months ago

[sandstrom]

Would be great if one could configure it to (1) keep the N most recent versions and (2) keep all younger than X days/months.

I think it's quite common that even if you make 20 releases over two weeks, you don't want to delete them (since they are recent), but when they are a few months old, it's fine to drop 10 of them (and only keep the 10 most recent).

Maybe something to consider?

Thanks for a great action! 🏅

[rubengees]

Sure, that could be added.

Out of curiosity, what is the difference between keeping the last say 10 version and keeping the last versions from one week? If you want to roll back you have enough older versions in any case or what is the use case here?

[sandstrom]

@rubengees If you're only keeping the versions from the last week, and don't make frequent releases (say once a month), after only a week you have no rollback options.

So basically any time you have inconsistent release schedules; e.g. 10 versions released over two weeks, then nothing for 3 months, then 1 release a month for 6 months.

Or if you don't know before hand what the release cadence will look like.

In these cases it would be great if one could configure it to (1) keep the N most recent versions and (2) keep all younger than X days/months.