Know which binaries remain downloadable.
Rolling plans protect the newest two releases in each channel and schedule older artifacts for removal; archive plans retain artifacts within storage allowance.
Rolling retention
Free / Hobby and Indie are rolling plans. After each publish, releases in that channel are ranked by publication and creation time:
- the latest two published releases have no prune date
- older releases receive a prune date if they do not already have one
- Free / Hobby uses 7 days
- Indie uses 14 days
The timer is scheduled from the publish that first makes a release older than the protected two; it is not calculated from the original release date.
Archive retention
Team, Business, and Enterprise use unlimited retention in the catalog. Their published releases have no scheduled prune date, but stored data still remains subject to the organization’s storage allowance and service terms.
What pruning changes
The retention job deletes the object from storage, clears its object key, and
marks the artifact with pruned_at. It does not delete the release or artifact
metadata row.
- the dashboard shows Pruned
- edge latest/history omit the inactive artifact
- direct artifact delivery returns
410 Gone - hosted history filters out releases with no active artifacts
Before downgrading
The Refund and Cancellation Policy warns that lower retention limits can cause older artifacts to be scheduled for deletion. Export required metadata and artifacts before plan access ends or a downgrade takes effect.