Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sync staging changes #263

Merged
merged 4 commits into from
Feb 26, 2024
Merged

Sync staging changes #263

merged 4 commits into from
Feb 26, 2024

Conversation

juanmardefago
Copy link
Collaborator

@juanmardefago juanmardefago commented Feb 8, 2024

Entity changes:

  • GraphNetwork
    • Added allocationCount which depicts the total amount of Allocation entities ever created
    • Added activeAllocationCount which depicts the current amount of open Allocation entities
  • GraphAccountMetadata renamed to GraphAccountMeta
  • SubgraphMetadata renamed to SubgraphMeta
  • SubgraphVersionMetadata renamed to SubgraphVersionMeta

Manifest changes:

  • Added auto pruning. This disables time travel queries.
  • Auto pruning settings:
    • 400 blocks for L1 (roughly over 1 hour on ethereum mainnet)
    • 15000 blocks for L2 (roughly over 1 hour on arbitrum one)
  • Bumped spec version to 1.0.0 to enable auto pruning

Dependencies changes:

  • Bumped contracts package from 5.3.3 to 6.2.0
  • Bumped graph-cli package from 0.48.0 to 0.68.0
  • Bumped graph-ts package from 0.29.3 to 0.32.0

Breaking changes:

  • Due to an issue on the query type generation, we needed to rename the metadata entities previously described. This changes the schema so it is considered a breaking change, but given that the previous schema was bugged (plural/singular query types for those entities wasn't being created properly, and thus, they didn't work), there shouldn't be any changes required to make this work, as the types that changed were not working before and couldn't have been used at all.
  • Auto pruning removes support for time travel queries older than the specified blocks for L1 (400) and L2 (15000). This breaks any app relying on historical data from this subgraph.

@juanmardefago juanmardefago merged commit 086871b into master Feb 26, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant