Releases: near/near-indexer-for-explorer
Releases · near/near-indexer-for-explorer
0.12.1
- Add support of Meta Transactions and upgrade near-indexer-primitives to
0.16.0
- Add new columns to
transaction_actions
andaction_receipt_actions
for supporting Meta Transactions (as usual, read the migration before applying if your DB is not empty) - Add betanet support
- Change start-from-interruption logic: we fail early (instead of track latest) if something goes wrong
0.11.0
- Migrate to NEAR Lake Framework,
indexer-explorer
no longer runs a NEAR node and instead consumes block from near-lake-indexer. - Stop tracking the data for
account_changes
andassets__fungible_token_events
. See more details in the discussion
Breaking Changes
- Storing genesis file is no longer possible (#327)
- Command line arguments for starting the indexer have changed slightly, see Readme for updated reference
- AWS credentials are now required for reading data from S3
- Tracking tables
account_changes
andassets__fungible_token_events
require enabling feature flags.
0.10.31
- Upgrade Indexer Framework to be based on
nearcore
version 1.30.0 patched
0.10.30
- Upgrade Indexer Framework to be based on nearcore version 1.30.0-rc.2
0.10.29
0.10.28
- Fixed function args extraction (
args->args_json
) for actions (action_receipt_actions
andtransaction_actions
tables). This bug affected all the records since 0.10.22 release. Consider removing and re-indexing all the records from the time you deployed 0.10.22+ release. See further details in #313
0.10.27
- Upgrade Indexer Framework to be based on nearcore version 1.29.0
- (MIGRATION REQUIRED) Add new complex index on action_receipt_actions (block_timestamp + index_in_actions) that is used for strict ordering
0.10.26
0.10.25
0.10.24
- Upgrade
nearcore
to1.29.0-rc.2
(according to nearcore release notes, it will require 3GB more RAM than before)