Skip to content

merge queue: checking epbs (ceaa8c0) and #1144 together - #1163

Closed
mergify[bot] wants to merge 2 commits into
epbsfrom
mergify/merge-queue/037e588946
Closed

merge queue: checking epbs (ceaa8c0) and #1144 together#1163
mergify[bot] wants to merge 2 commits into
epbsfrom
mergify/merge-queue/037e588946

Conversation

@mergify

@mergify mergify Bot commented Jul 22, 2026

Copy link
Copy Markdown

🎉 This pull request has been checked successfully and will be merged soon. 🎉

Branch epbs (ceaa8c0) and #1144 are queued together for merge.

This pull request has been created by Mergify to check the mergeability of #1144.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule default for merge:

  • check-success=cli-reference-check
  • check-success=run-local-testnet
  • check-success=test-suite-success

Required conditions to stay in the queue:

---
checking_base_sha: ceaa8c00c6db7411f04cd0f4c25804b879ce35b5
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 1144
    scopes: []
scopes: []
...

petarjuki7 and others added 2 commits July 22, 2026 15:46
…rStore backend

Construct Lighthouse's ProposerPreferencesService with AnchorValidatorStore
and start it via start_update_service(), inside the existing
is_gloas_scheduled() gate next to PayloadAttestationService. Completes the
Anchor-side ProposerPreferences pipeline: LH's service drives
sign_proposer_preferences (#1063) per validator per epoch, dispatching both
proposal_data and signing through Anchor's ValidatorStore impl.

Part of #1064.
@github-actions

Copy link
Copy Markdown

Your PR title doesn't follow the Conventional Commit guidelines.

Example of valid titles:

  • feat: add new user login
  • fix: correct button size
  • docs: update README

Usage:

  • feat: Introduces a new feature
  • fix: Patches a bug
  • chore: General maintenance tasks or updates
  • test: Adding new tests or modifying existing tests
  • perf: Performance improvements
  • refactor: Changes to improve code structure
  • docs: Documentation updates
  • ci: Changes to CI/CD configurations
  • revert: Reverts a previously merged PR

Breaking Changes

Breaking changes are noted by using an exclamation mark. For example:

  • feat!: changed the API
  • chore(node)!: Removed unused public function

Help

For more information, follow the guidelines here: https://www.conventionalcommits.org/en/v1.0.0/

@mergify mergify Bot closed this Jul 22, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/037e588946 branch July 22, 2026 17:56
@codecov-commenter

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 0% with 9 lines in your changes missing coverage. Please review.
⚠️ Please upload report for BASE (epbs@ceaa8c0). Learn more about missing BASE report.

Files with missing lines Patch % Lines
anchor/client/src/lib.rs 0.00% 9 Missing ⚠️
Additional details and impacted files
@@           Coverage Diff           @@
##             epbs    #1163   +/-   ##
=======================================
  Coverage        ?   68.51%           
=======================================
  Files           ?      164           
  Lines           ?    31443           
  Branches        ?        0           
=======================================
  Hits            ?    21544           
  Misses          ?     9899           
  Partials        ?        0           
Flag Coverage Δ
rust 68.51% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

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.

2 participants