Repository deletion and restore
Understand Ravenstash repository deletion, access revocation, restore expectations, and current lifecycle boundaries.
Updated 2026-06-24
Deleting a Ravenstash repository is intentionally explicit because package-manager URLs stop working immediately.
Private repository deletion
Deleting a private repository soft-deletes it, sets deletion metadata, and revokes access immediately.
The current backend hard-deletes soft-deleted repositories and their object-storage artifacts after a seven-day grace period.
Restore
Admin operators can restore soft-deleted private repositories from the backoffice during the grace period. Remote repositories are not restorable.
Upstream dependencies
Deletion is blocked when a repository is used as an upstream by another repository. Remove or change dependent upstream configuration before deleting the repository.
Rename caution
Repository public IDs are mutable for private repositories. Renaming a repository changes package-manager upload and download URLs immediately.
