Skip to content

chore(chain): update checkpoints - #11148

Merged
mergify[bot] merged 1 commit into
mainfrom
chore/update-checkpoints
Aug 5, 2026
Merged

chore(chain): update checkpoints#11148
mergify[bot] merged 1 commit into
mainfrom
chore/update-checkpoints

Conversation

@zebra-release

@zebra-release zebra-release Bot commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

Automated checkpoint update from the integration test run.

Source: Integration test run #31010112881

Checkpoints are consensus-critical. Verify the new hashes against the source run before merging.

@zebra-release zebra-release Bot added A-release Area: Zebra releases and release management C-enhancement Category: This is an improvement labels Jul 29, 2026
@zebra-release
zebra-release Bot force-pushed the chore/update-checkpoints branch from dd0bcb8 to e476efa Compare July 30, 2026 18:37
@zebra-release
zebra-release Bot force-pushed the chore/update-checkpoints branch from e476efa to b630b06 Compare July 31, 2026 02:36
@zebra-release
zebra-release Bot force-pushed the chore/update-checkpoints branch from b630b06 to 34a23da Compare July 31, 2026 16:04
@zebra-release
zebra-release Bot force-pushed the chore/update-checkpoints branch from 34a23da to 3840d1e Compare July 31, 2026 18:40

@conradoplg conradoplg left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Weird, why didn't it update with a 400 gap in mainnet?

@conradoplg conradoplg left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Looking into it, the weird gap is because zebra-checkpoints also considers the block size when computing the gaps, and they have been larger than usual. So everything looks good

@mergify mergify Bot added the queued label Aug 5, 2026
@mergify

mergify Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Merge Queue Status

  • Entered queue2026-08-05 16:30 UTC · Rule: batched · triggered by rule move to any queue if GitHub Rulesets are satisfied
  • Checks passed · on draft merge queue: checking main (d098d01) and #11148 together #11191
  • Merged2026-08-05 16:31 UTC · at f3b941e5c0deab8a40a10bc58909a22273746502 · merge

This pull request spent 1 minute 49 seconds in the queue, including 48 seconds running CI.

Required conditions to merge
  • #review-threads-unresolved = 0 [🛡 GitHub repository ruleset rule PR Requirements]
  • github-review-approved [🛡 GitHub branch protection]
  • github-review-approved [🛡 GitHub repository ruleset rule PR Requirements]
  • any of [🛡 GitHub repository ruleset rule PR Requirements]:
    • check-success = @github-actions/lint
    • check-neutral = @github-actions/lint
    • check-skipped = @github-actions/lint
  • any of [🛡 GitHub repository ruleset rule PR Requirements]:
    • check-success = test-crates
    • check-neutral = test-crates
    • check-skipped = test-crates
  • any of [🛡 GitHub repository ruleset rule PR Requirements]:
    • check-success = unit-tests
    • check-neutral = unit-tests
    • check-skipped = unit-tests
  • any of [🛡 GitHub repository ruleset rule PR Requirements]:
    • check-success = @github-actions/pr-gate-result
    • check-neutral = @github-actions/pr-gate-result
    • check-skipped = @github-actions/pr-gate-result

@mergify
mergify Bot merged commit 8e9ff3b into main Aug 5, 2026
110 of 114 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-release Area: Zebra releases and release management C-enhancement Category: This is an improvement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant