From cc3172ac79af44e53fd0dd3dab99f27933d011c8 Mon Sep 17 00:00:00 2001 From: Yash Jagtap Date: Fri, 24 May 2024 11:25:21 +0530 Subject: [PATCH 1/5] add Timestamp scalar --- website/pages/en/developing/creating-a-subgraph.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/website/pages/en/developing/creating-a-subgraph.mdx b/website/pages/en/developing/creating-a-subgraph.mdx index 89e2a09e7102..388e8d79855f 100644 --- a/website/pages/en/developing/creating-a-subgraph.mdx +++ b/website/pages/en/developing/creating-a-subgraph.mdx @@ -281,6 +281,7 @@ We support the following scalars in our GraphQL API: | `Int8` | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. | | `BigInt` | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`. | | `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits. | +| `Timestamp` | Scalar for `timestamp` fields for timeseries and aggregations. | #### Enums From a6176ad9ee6169583ae4c1d7a81e46414d7ce66c Mon Sep 17 00:00:00 2001 From: Yash Jagtap Date: Fri, 24 May 2024 11:54:19 +0530 Subject: [PATCH 2/5] update Subgraph Studio archive policy --- .../pages/ar/deploying/deploying-a-subgraph-to-hosted.mdx | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/website/pages/ar/deploying/deploying-a-subgraph-to-hosted.mdx b/website/pages/ar/deploying/deploying-a-subgraph-to-hosted.mdx index d73262114e2e..a60e0b42b2b4 100644 --- a/website/pages/ar/deploying/deploying-a-subgraph-to-hosted.mdx +++ b/website/pages/ar/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: +- The version is not published to the network (or pending publish) +- The version is not indexing a "special case" chain (polygon-zkevm, zksync-era, base, etc.) +- The version was created 45 or more days ago +- The subgraph hasn't been queried in 30 days -When a subgraph version isn’t queried for over 45 days, that version is archived. +In addition, when a new version is deployed, the N-2 version of the Subgraph is archived if it has not been published Every subgraph affected with this policy has an option to bring the version in question back. From 8a8e16c6809c6c49d7ac724bbad40c6310917454 Mon Sep 17 00:00:00 2001 From: Yash Jagtap Date: Fri, 24 May 2024 12:04:01 +0530 Subject: [PATCH 3/5] fix style with prettier --- website/pages/ar/deploying/deploying-a-subgraph-to-hosted.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/website/pages/ar/deploying/deploying-a-subgraph-to-hosted.mdx b/website/pages/ar/deploying/deploying-a-subgraph-to-hosted.mdx index a60e0b42b2b4..2779f640cc33 100644 --- a/website/pages/ar/deploying/deploying-a-subgraph-to-hosted.mdx +++ b/website/pages/ar/deploying/deploying-a-subgraph-to-hosted.mdx @@ -285,6 +285,7 @@ Developers will be notified by email if one of their subgraphs has been marked a ## Subgraph Studio subgraph archive policy A Subgraph version in Studio is archived if and only if it meets the following criteria: + - The version is not published to the network (or pending publish) - The version is not indexing a "special case" chain (polygon-zkevm, zksync-era, base, etc.) - The version was created 45 or more days ago From a250b7a90382352676e7b6f1ff72264c07edcc39 Mon Sep 17 00:00:00 2001 From: Yash Jagtap Date: Fri, 24 May 2024 21:41:05 +0530 Subject: [PATCH 4/5] fix requested changes --- website/pages/ar/deploying/deploying-a-subgraph-to-hosted.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/pages/ar/deploying/deploying-a-subgraph-to-hosted.mdx b/website/pages/ar/deploying/deploying-a-subgraph-to-hosted.mdx index 2779f640cc33..14e800c62c12 100644 --- a/website/pages/ar/deploying/deploying-a-subgraph-to-hosted.mdx +++ b/website/pages/ar/deploying/deploying-a-subgraph-to-hosted.mdx @@ -284,13 +284,13 @@ Developers will be notified by email if one of their subgraphs has been marked a ## Subgraph Studio subgraph archive policy -A Subgraph version in Studio is archived if and only if it meets the following criteria: +A subgraph version in Studio is archived if and only if it meets the following criteria: - The version is not published to the network (or pending publish) - The version is not indexing a "special case" chain (polygon-zkevm, zksync-era, base, etc.) - 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, the N-2 version of the Subgraph is archived if it has not been published +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. From f4bd2e6be84858e569ccb468a15d62d7d899375b Mon Sep 17 00:00:00 2001 From: Yash Jagtap Date: Sat, 25 May 2024 10:58:03 +0530 Subject: [PATCH 5/5] remove special case chains and removed ar change --- .../ar/deploying/deploying-a-subgraph-to-hosted.mdx | 9 ++------- .../en/deploying/deploying-a-subgraph-to-hosted.mdx | 8 ++++++-- 2 files changed, 8 insertions(+), 9 deletions(-) diff --git a/website/pages/ar/deploying/deploying-a-subgraph-to-hosted.mdx b/website/pages/ar/deploying/deploying-a-subgraph-to-hosted.mdx index 14e800c62c12..d73262114e2e 100644 --- a/website/pages/ar/deploying/deploying-a-subgraph-to-hosted.mdx +++ b/website/pages/ar/deploying/deploying-a-subgraph-to-hosted.mdx @@ -284,13 +284,8 @@ Developers will be notified by email if one of their subgraphs has been marked a ## Subgraph Studio subgraph archive policy -A subgraph version in Studio is archived if and only if it meets the following criteria: +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. -- The version is not published to the network (or pending publish) -- The version is not indexing a "special case" chain (polygon-zkevm, zksync-era, base, etc.) -- 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. +When a subgraph version isn’t queried for over 45 days, that version is archived. Every subgraph affected with this policy has an option to bring the version in question back. 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 0940b91ad132..b5d4b2c7297b 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.