Releases: graphprotocol/graph-network-subgraph
Re-sync on different ipfs hash
v0.15.1 Non-change to trigger redeploy on different IPFS hash
Improved manifest parsing and query fee breakdown on Epoch
v0.15.0 Added taxed and total amounts for Epoch qfees
Removed grafting configuration for full resync
v0.14.4 Removed grafting configuration for full resync
Hotfix for Deployment manifest parsing
Fixes a crash due to an invalid manifest trying to be parsed.
Full fix will be deployed later, in the meantime this grafted version will allow indexing to continue, but will be missing some data (mainly schema
and network
fields for SubgraphDeployment
entities created after the errored block).
Non-IPFS versions of the subgraph are not affected
Fix currentSignalledTokens and workflows graph-cli mismatch
v0.14.2 Removed graph-cli global from workflows
Hotfix for RewardsDenylistUpdated bug
v0.14.1 Added graft base to quickly replace mainnet subgraph
Added support for new GNS contract
This release adds support for the new transfer ownership feature for Subgraphs (GNS upgrade), while still remaining backwards compatible via entity duplication.
The GNS upgrade changes the ID of the subgraphs, so we reflect this on the Subgraph
entity, but we keep a duplicate entity for Subgraph
, SubgraphVersion
and NameSignal
entities that were created before the upgrade, so that anyone using the old IDs will still keep working.
Entity changes:
Subgraph
,SubgraphVersion
andNameSignal
:- Added
entityVersion
field. Denotes the entity version, currently only1
and2
are the possible values. A value of1
denotes that the entity is represented with the OLD ID format for subgraphs, a value of2
denotes that the entity is represented with the NEW ID format for subgraphs. - Added
linkedEntity
field. Denotes the duplicate entity (if one exists). All entities that were created before the upgrade will have both aentityVersion: 1
andentityVersion: 2
representation of the same entity, and both will be linked through this field.
- Added
Sugraph
- Added
migrated
field that denotes whether the subgraph has been migrated to the new GNS representation. Once it's migrated it will be represented in the contracts as an NFT that can be transferred, otherwise it won't be possible to transfer ownership yet. - Added
nftID
field. Denotes theBigInt
(decimal base) representation of theSubgraph
ID (ERC721 compatible), since theid
field uses the same bytes but in a base58 representation. - Added
oldID
field. Denotes theid
of the entity represented using the old format. - Added
creatorAddress
field. Denotes the address of theGraphAccount
that created the subgraph. It's used as the first part for the ID for theSubgraph
- Added
subgraphNumber
field. Denotes the sequential number (autoincremental id) used as the second part for the ID of theSubgraph
. - Added
nftImage
field. Denotes the IPFS file used as the image for the NFT for theSubgraph
- Added
ipfsMetadataHash
field. Denotes the metadataHash as an valid IPFS hash (base58 IPFS multihash)
- Added
Upgrade to latest versions of graph-cli and graph-ts
v0.13.0 Updated graph-cli and graph-ts to fix non-nullables being initialized
Hotfix
This release fixes the crash for this subgraph on Dec. 27th.
Upgrade to 0.0.5 apiVersion and some minor changes
- Updates the apiVersion on all data sources to 0.0.5.
- Updates the
graph-cli
andgraph-ts
dependency versions. - Fixes
forcedClosures
in theIndexer
entity (previously it was badly counting which allocation closures where forced, since it only took into consideration scenarios where the address of the indexer was used to close it, but it didn't consider operators). - Fixes
version
in theSubgraphVersion
entity (previously it was initialized as 0 but never updated). - Fixes some linter issues.