Hobby projects retain fewer deployments to free up storage
Hobby projects now keep only their 3 most recent production deployments and 3 most recent deployments of any type, with older deployments deleted immediately if a team exceeds the 10GB storage limit. This change helps dormant projects stop consuming storage needed by active projects.
Hobby projects now retain fewer deployments past the 30-day retention window. Hobby teams get 10GB of . Every deployment you keep uses some of it, and going over the limit can block you from deploying until you free some up. for Hobby teams now deletes old deployments sooner, so dormant projects stop holding storage that your active projects need.Deployment StorageDeployment Retention
Each Hobby project now keeps its 3 most recent production deployments, plus its 3 most recent deployments of any type, regardless of age. Preview deployments no longer get their own protection. Your current production deployment is still never deleted, and aliased and active-branch deployments are still protected. See the .full list of exceptions in the docs
If your team is over the 10GB limit, deployments outside those exceptions are now deleted immediately instead of after 30 days.
To stay under the limit, see , or upgrade to , where storage is billed at $0.10 per GB per month.how to optimize your Deployment Storage usagePro
Source: original entry ↗