v0.36.1
Note for indexers upgrading from a manually-downgraded version
This release requires Postgres schema migrations to be run. If your database was manually downgraded by running
down.sql
scripts, you need to take care to remove the related entries from the__diesel_schema_migrations
table. For example; if you downgraded fromv0.36.0
tov0.35.1
, you likely ran the following migrations manually:store/postgres/migrations/2024-06-11-084227_track-more-features-in-subgraph-features/down.sql store/postgres/migrations/2024-07-22-140930_track_synced_date/down.sql store/postgres/migrations/2024-08-14-205601_store_synced_at_block/down.sql store/postgres/migrations/2024-10-01-100427_create_graphman_command_executions_table/down.sql
As such, you'll need to execute the following query in all shards before upgrading again:
DELETE FROM __diesel_schema_migrations WHERE version IN ( '20241001100427', '20240814205601', '20240722140930', '20240611084227' )If you ran down scripts for only some of these migrations, you need to only remove those from the
__diesel_schema_migrations
table.This will ensure that migrations will automatically be re-run on upgrade to
v0.36.1
, restoring the database to a sane state.
Improvements
This release addresses several issues found in v0.36.0
, notably:
- Remove confusing IPFS warning messages (#5723)
- Better concurrent IPFS client selection (#5723)
- Bug with handling of enum arrays that can cause subgraphs to fail (#5372)
Additionally, this release has been tested for an extended period on the Upgrade Indexer, ensuring
issues in v0.36.0
related to IPFS, block ingestion, and migrations work as intended.
Additional changes:
- Add subcommand description to
graphman deploy
(#5744) - Display log message argument when calling
log.critical
(#5744)
Thanks to @lutter, @shiyasmohd, and @isum for contributing to this release.
Full Changelog: v0.36.0...v0.36.1