Skip to content

chore(deps): update ghcr.io/streamingfast/firehose-ethereum docker tag to v2.25.0 - #59

Open
renovate[bot] wants to merge 2 commits into
mainfrom
renovate/ghcr.io-streamingfast-firehose-ethereum-2.x
Open

renovate[bot] wants to merge 2 commits into
mainfrom
renovate/ghcr.io-streamingfast-firehose-ethereum-2.x

Conversation

@renovate

@renovate renovate Bot commented Nov 12, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
ghcr.io/streamingfast/firehose-ethereum minor v2.24.1 → v2.25.0

Release Notes

streamingfast/firehose-ethereum (ghcr.io/streamingfast/firehose-ethereum)

v2.25.0

Compare Source

Added
  • Substreams: --substreams-tier1-status-page-template takes the path to a Go html/template file that tier1 serves to anything doing GET / on its endpoint, with the chain name, readiness, liveness and head block ({{ .ChainName }}, {{ .Ready }}, {{ .Live }}, {{ .HeadBlockNum }}, {{ .HeadBlockID }}, {{ .HeadBlockTime }}). A client asking for application/json gets the same data as JSON. The file is reloaded when it changes. The page is served whatever the Accept header says and is not subject to --substreams-tier1-enforce-compression, like /healthz.

  • TRX_TYPE_ACCOUNT_ABSTRACTION = 121 in sf.ethereum.type.v2, for the account abstraction transaction (type byte 0x79) of the AA Transaction Type proposal split out of EIP-8130, which Base activates with its Everest upgrade. Its fields are in the new TransactionTrace.account_abstraction_trx_input: the nonce key, the payer, the validity window, the metadata, the account changes (an EIP-7702 style delegation, or the creation and configuration of a Keystore account, EIP-8130), the signed calls grouped in phases, each linked to the call that executed it, and the sender's authentication when the sender does not sign with its secp256k1 key. committed_phases, in the new TransactionReceipt.account_abstraction_trx_output, counts the phases that committed. A transaction of this type can be FAILED and still keep the state of the phases that committed before the one that reverted, see the TransactionTrace.status documentation.

  • TRX_TYPE_OPTIMISM_POST_EXEC = 125 in sf.ethereum.type.v2, for Optimism's post-exec transaction (type byte 0x7d), which OP Stack chains activate with the Lagoon upgrade. It is a system transaction appended by the block builder: its sender is the zero address, its input is the RLP-encoded post-exec payload, it runs no EVM code (no calls) and its gas used is 0.

Changed
  • Bump firehose-core to v1.21.2 and substreams to v1.27.0, with the matching dauth. The Firehose incoming request logs, as well as the incoming Substreams Blocks request and Estimate logs, now carry auth_method, auth_jwt_lifetime_bucket, auth_jwt_iat and auth_jwt_exp (firehose-core#319, substreams#1039), to follow the phase out of long-lived JWTs.

  • In sf.ethereum.type.v2, TransactionTrace.morph_tx_config (MorphTxConfig) is renamed morph_trx_input (MorphTrxInput), TransactionTrace.morph_l1_message_config (MorphL1MessageConfig) is renamed morph_l1_message_trx_input (MorphL1MessageTrxInput), and TransactionReceipt.morph_receipt_config (MorphReceiptConfig) is renamed morph_trx_output (MorphTrxOutput). The field numbers are unchanged, so blocks already written decode the same, but code using the generated bindings or the JSON field names must use the new names.

  • Bump dstore: an S3 upload now fails when its reader fails partway instead of storing a truncated object, S3 copies run server-side, and zstd stores accept compression_config (level, window, decoder lowmem and pool) in the store URL.

  • Bump dsession to fix two worker counter leaks.

Fixed
  • Blocks built from JSON-RPC (tools compare-blocks-rpc and the RPC poller) now set TransactionTrace.blob_gas and TransactionReceipt.blob_gas_used only for blob transactions (type 3). On OP-stack chains since Jovian, receipts report the transaction's data-availability footprint as blobGasUsed on every transaction, which was copied as blob gas.

  • github.com/klauspost/compress is updated from v1.20.1 to v1.20.2 to fix CVE-2026-116591 (High, zstd DecodeAll crash on crafted input, GHSA-fpmh-frq8-7rj8).

  • github.com/go-jose/go-jose/v4 is updated from v4.1.4 to v4.1.6 to fix CVE-2026-116587 (High, inefficient algorithmic complexity).

  • Bump eth-go to 736af9a, which closes the response body when the RPC endpoint answers with an HTTP error status (eth-go#18). Before, every error response (for example a 429 from a rate-limited endpoint) leaked its connection and two goroutines, so Substreams eth_call and eth_getBalance requests to a failing endpoint grew the open file count until the process hit its limit.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Risk: medium. Cursor Bugbot was not present on this PR, so that signal was skipped. This is a one-line appVersion bump on charts/substreams-tier-2/Chart.yaml (v2.24.1 → v2.25.0) with no policy requiring human review, so I approved.

Open in Web View Automation 

Sent by Cursor Approval Agent: Pull Request Router and Approver

@renovate

renovate Bot commented Nov 12, 2026

Copy link
Copy Markdown
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants