Skip to content

chore(deps): update ghcr.io/streamingfast/firehose-core docker tag to v1.21.2 - #58

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

renovate[bot] wants to merge 2 commits into
mainfrom
renovate/ghcr.io-streamingfast-firehose-core-1.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-core patch v1.21.1 → v1.21.2

Release Notes

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

v1.21.2

Compare Source

Added
  • Reader: reader_node_one_block_upload_pending_files and reader_node_one_block_upload_oldest_pending_seconds report the one-block files waiting in the local staging directory and how long the oldest has waited, measured at each upload pass. When the one-block store is slow or down the reader keeps reading blocks and serving its relayers, and its /healthz stays ready, so this backlog was not visible anywhere until the disk filled up.
  • Tools: firecore tools stats-merged-blocks no longer leaves files missing the datasize/itemcount/timestamp annotation out of its total. Their compressed size comes from the listing, and their block count and uncompressed size are estimated from the annotated files in the range (same blocks per file, same compression ratio). They are reported apart as unannotated in --json and as an UNANNOTATED* row in the table, and are included in total. The months still cover annotated files only. unannotated_files is unchanged.
  • Tools: firecore tools resize-merged-blocks writes the datasize, itemcount and timestamp object metadata on every file it writes to Google Cloud Storage, as the merger does. Files it wrote before carry none and need firecore tools annotate-merged-blocks.
Fixed
  • Tools: firecore tools stats-merged-blocks now reports the first listed file as first_block_seen (and Blocks seen in the table) even when that file is unannotated. It used to report the first annotated file instead.
Changed
  • Merger: logs its unlinkable-blocks limit once at startup (merger unlinkable-blocks circuit breaker configured, with max_unlinkable_blocks and source), so operators can confirm a MERGER_MAX_UNLINKABLE_BLOCKS override took effect. The limit is now resolved once per run instead of on every walk; behavior is unchanged.
  • Bumped github.com/klauspost/compress to v1.20.2 to fix CVE-2026-116591.
  • Bumped substreams to v1.27.0, see its release notes.
  • Bumped 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.
  • Bumped dsession to fix two worker counter leaks.
Fixed
  • Merger: jumping ahead to bundles published by another merger no longer lets the pruner delete one-block files of bundles still being uploaded.
  • Merger: when two mergers run against the same stores, the slower one no longer shuts down when the faster one prunes the one-block files of a bundle it is still merging. If the merge fails and the bundle already exists in the merged-blocks store, it is treated as merged.

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. Approved: this is a one-line firehose-core appVersion patch bump (v1.21.1 → v1.21.2), Cursor Bugbot was not present, and nothing in the current evidence needs human review.

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