v1.12.0

Server-side

• Fix a thread leak in cursor resolution resulting in a bad value for active_connections metric
• Fix detection of accepted gzip compression when multiple values are sent in the Grpc-Accept-Encoding header (ex: Python library)
• Properly accept and compress responses with gzip for browser HTTP clients using ConnectWeb with Accept-Encoding header
• Allow setting subscription channel max capacity via SOURCE_CHAN_SIZE env var (default: 100)
• Added tier1 app configuration option to limit max active requests a single instance can accept before starting to reject them with 'Unavailable' gRPC code.
• Added tier1 & tier2 app new Prometheus metric substreams_{tier1,tier2}_rejected_request_counter, to track rejected request, especially when hard limit is reached.

Client-side

• improvements to 'tools prometheus-explorer'

  • change flags lookup_interval and lookup_timeout to --interval and --timeout
  • now support relative block (default is now: -1) and does not use 'final-blocks-only' flag on request
  • add --max-freshness flag to check for block age (when using relative block)
  • add substreams_healthcheck_block_age_ms prometheus metric
  • --block-height is now a flag instead of a positional argument
  • improve logging
  • removed "3 retries" that were built in and causing more confusion

• add User-Agent headers depending on the client command

v1.11.3

Server-side

• Fixed: detection of gzip compression on 'connect' protocol (js/ts clients)
• Added: tier1.Config EnforceCompression to refuse incoming connections that do not support GZIP compression (default: false)

v1.11.2

Server-side

• Fix too many memory allocations impacting performance when stores are used

CLI

• Force topological ordering of protobuf descriptors when 'packing' an spkg (affecting current substreams-js clients)
• Allow substreams pack to be able to do a "re-packing" of an existing spkg file. Useful to apply the protobuf descriptor ordering fix.

Docker image

• Rebuilt of v1.11.1 to generate Docker latest tag with revamp Docker image building.
• Substreams CLI is now built with using Ubuntu 22, previous releases were built using Ubuntu 20.
• Substreams Docker image is now using ubuntu:22 as its base, previous releases were built using ubuntu:20.04.

v1.11.1

• Fix the gui breaking when the network field is not set in the spkg
• Fixed SUBSTREAMS_REGISTRY_TOKEN environment variable not taking precedence over the registry-token file.

v1.11.0

• Commands run, gui and info now accept the new standard package definition (ex: ethereum-common@latest) to reference an spkg file from https://substreams.dev.
• Changed substreams run: the two positional parameters now align with gui: [package [module_name]]. The syntax substreams run <module_name> is not accepted anymore.
• Added substreams publish to publish a package on the substreams registry (check on https://substreams.dev).
• Added substreams registry to login and publish on the substreams registry (check on https://substreams.dev).
• Added substreams tools extract-wasm to extract a wasm file from a substreams package.

v1.10.11

• Add avalanche-mainnet to the CLI.

v1.10.10

• Fix substreams gui selecting the wrong module in the 'outputs' view if there is no output the selected output_module.
• Add the block 'age' printed clock headers in thesubstreams run command.

v1.10.9

• Supports Vara mainnet, Vara testnet, Mantra testnet, Mantra mainnet
• Add support for Base58 decoding in substreams gui
• Fix package download for substreams gui

v1.10.8

Server

Note All caches for stores using the updatePolicy set_sum (added in substreams v1.7.0) and modules that depend on them will need to be deleted, since they may contain bad data.

• Fix bad data in stores using set_sum policy: squashing of store segments incorrectly "summed" some values that should have been "set" if the last event for a key on this segment was a "sum"
• Fix panic in initialization (metrics sender not set)

v1.10.7

• Fix small bug making some requests in development-mode slow to start (when starting close to the module initialBlock with a store that doesn't start on a boundary)
• Fixed substreams build creating a buf.gen.yaml file with absolute paths (should be relative)
• Removed --show-generated-buf-gen flag to substreams protogen
• Bumped neoeinstein-prost version in auto-generated buf.gen.yaml file when using substreams protogen or substreams build (compatible with new substreams-0.6 and prost-0.13)