fix: Shard IDs is mixed-up leading to shard filenames to be incorrect (…

…#119)
near · Dec 12, 2024 · 34ad8f8 · 34ad8f8
1 parent dd292fa
commit 34ad8f8
Show file tree

Hide file tree

Showing 4 changed files with 106 additions and 100 deletions.
diff --git a/.cargo/config.toml b/.cargo/config.toml
@@ -1,2 +1,2 @@
 [env]
-NEARCORE_VERSION = "2.4.0-2797449"
+NEARCORE_VERSION = "2.4.0-7b3a53e"
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,5 +1,11 @@
 # Changelog
 
+## 2.4.1
+
+* Switch to the Indexer Framework 2.4.0 but with the fix for shard id. See [issue#118](https://github.com/near/near-lake-indexer/issues/118)
+
+Once this release is deployed we expect new data to have correct shard ids in the filenames and correct data. The data that was indexed with the wrong shard id will be reindexed as soon as possible.
+
 ## 2.4.0
 
 * Upgrade Indexer Framework to be based on [nearcore 2.4.0](https://github.com/near/nearcore/releases/tag/2.4.0)