v4.2.1

• Bump substreams to v1.10.3 to support new manifest data like protobuf:excludePaths

v4.2.0

• Added the --cursor-table and --history-table flags to allow running to sinks on the same database (be careful that you have no collision in table names)
• bumped substreams to v1.8.2, add some default network endpoints

v4.0.3

• Fix another case where 'infinite-retry' would not work and the program would stop on an error.
• Enable multiple Substreams authentication methods (API key, JWT), using flags --api-key-envvar and --api-token-envvar.
• Deprecates the use of SF_API_TOKEN environment variable, now use default SUBSTREAMS_API_TOKEN or set your own using --api-token-envvar.

v4.0.2

• Fixed spurious error reporting when the sinker is terminating or has been canceled.

• Updated substreams dependency to latest version v1.3.7.

v4.0.1

• Fixed the timestamp parsing in Clickhouse dialect.
• Fixed the schema in the tutorial for clickhouse.
• Add --network flag to override the default value in the manifest or spkg

v4.0.0

Highlights

• This release brings support for managing reorgs in Postgres database, enabled by default when --undo-buffer-size to 0.

Breaking changes

• A change in your SQL schema may be required to keep existing substreams:SQL integrations working:
  • The presence of a primary key (single key or composite) is now MANDATORY on every table.
  • The sf.substreams.sink.database.v1.TableChange message, generated inside substreams, must now exactly match its primary key with the one in the SQL schema.
  • You will need to re-run setup on your existing PostgreSQL databases to add the substreams_history table. You can use the new --system-tables-only flag to perform only that.
• Since reorgs management is not yet supported on Clickhouse, users will have to set --undo-buffer-size to a non-zero value (12 was the previous default)

Fixes

• Bump version of schema dependency to fix errors with newer Clickhouse versions now using system.tables table instead of information_schema.tables view.
• Support more networks with default mappings (ex: solana, soon: optimism, soon: bitcoin)
• Add command "create-user " to help creating more SQL users, read-only or otherwise
• Add 'enabled' field under "DBTConfig"
• Removed PgwebFrontend and WireProtocolAccess fields from the SinkConfig message: they will now be deployed when on a development environment, so they are not mentionned here anymore.

v4.0.0-rc.3

• Fix a critical bug breaking the reorg management when more than one row needs to be reverted.

v4.0.0-rc.2

• Support more networks with default mappings (ex: solana, soon: optimism, soon: bitcoin)
• Add command "create-user " to help creating more SQL users, read-only or otherwise
• add 'enabled' field under "DBTConfig"
• Removed PgwebFrontend and WireProtocolAccess fields from the SinkConfig message: they will now be deployed when on a development environment, so they are not mentionned here anymore.

protodefs-v1.0.7

remove wire_protocol_access from Service

protodefs-v1.0.6

remove pgweb from Service definition, add enabled field to DBTConfig