From 89cdfbafaf468a21910fe216f6951621691edaa6 Mon Sep 17 00:00:00 2001 From: Yash Jagtap Date: Thu, 30 May 2024 04:32:49 +0530 Subject: [PATCH] update Subgraph Studio archive policy (#684) * add Timestamp scalar * update Subgraph Studio archive policy * fix style with prettier * fix requested changes * remove special case chains and removed ar change --------- Co-authored-by: azf20 --- .../pages/en/deploying/deploying-a-subgraph-to-hosted.mdx | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/website/pages/en/deploying/deploying-a-subgraph-to-hosted.mdx b/website/pages/en/deploying/deploying-a-subgraph-to-hosted.mdx index 422a2c73c7bf..f1be54725c2b 100644 --- a/website/pages/en/deploying/deploying-a-subgraph-to-hosted.mdx +++ b/website/pages/en/deploying/deploying-a-subgraph-to-hosted.mdx @@ -284,8 +284,12 @@ Developers will be notified by email if one of their subgraphs has been marked a ## Subgraph Studio subgraph archive policy -When a new version of a subgraph is deployed, the previous version is archived (deleted from the graph-node DB). This only happens if the previous version is not published to The Graph's decentralized network. +A subgraph version in Studio is archived if and only if it meets the following criteria: -When a subgraph version isn’t queried for over 45 days, that version is archived. +- The version is not published to the network (or pending publish) +- The version was created 45 or more days ago +- The subgraph hasn't been queried in 30 days + +In addition, when a new version is deployed, if the subgraph has not been published, then the N-2 version of the subgraph is archived. Every subgraph affected with this policy has an option to bring the version in question back.