Name | Modified | Size | Downloads / Week |
---|---|---|---|
Parent folder | |||
README.md | 2025-05-30 | 1.4 kB | |
v0.39.1 source code.tar.gz | 2025-05-30 | 2.5 MB | |
v0.39.1 source code.zip | 2025-05-30 | 3.1 MB | |
Totals: 3 Items | 5.6 MB | 4 |
v0.39.1
Critical Fix
Event Transaction Log Index
- Reverted transaction log index behavior: Fixed a regression introduced in v0.38.0 where
event.transactionLogIndex
was inadvertently changed to return the actual transaction log index instead of the log index (#6042)
Impact: This change in v0.38.0 caused subgraph failures with duplicate ID errors for subgraphs using event.transactionLogIndex
for entity ID generation. It could also lead to POI divergence between indexers running different versions.
Note: While this restores the previous behavior, event.transactionLogIndex
continues to return the same value as event.logIndex
(not the actual transaction log index). Subgraph developers should use event.logIndex
for unique log identification.
Upgrade Notes
Indexers running v0.38.0 who have synced subgraphs that use event.transactionLogIndex
should:
1. Upgrade to v0.39.1
2. Rewind affected subgraphs to before they were synced with v0.38.0
3. Resync to ensure POI convergence with the network
Contributors
Thanks to @lutter for the quick fix and the indexer community for identifying and helping diagnose this issue.
Full changelog: https://github.com/graphprotocol/graph-node/compare/v0.39.0...v0.39.1