Repository navigation
chore(deps): return Lighthouse to sigp unstable 73e4dc12 - #1322
Merged
shane-moore merged 1 commit intoSep 28, 2026
Merged
Conversation
sigp/lighthouse#9959 merged upstream, so every Lighthouse dependency leaves the shane-moore/lighthouse fork pin from sigp#1317 and returns to sigp/lighthouse unstable 73e4dc12. The #9959 code is identical to what the fork carried; the bump also picks up four fork-choice commits that Anchor does not use.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## epbs #1322 +/- ##
=======================================
Coverage 80.79% 80.79%
=======================================
Files 179 179
Lines 41224 41224
=======================================
Hits 33307 33307
Misses 7917 7917
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem, Evidence, and Context (Required)
shane-moore/lighthouse1513afc4) to carry Apply Beacon API amendments to payload attestation data endpoint lighthouse#9959 before it merged.73e4dc12, which is the current Lighthouseunstablehead, so the fork pin is no longer needed.Change Overview (Required)
sigp/lighthouseat73e4dc120dfb49fbc5123d4fad42d935a94f368f. The lockfile diff is only those crates' source lines; no crates.io versions change.Risks, Trade-offs, and Mitigations (Required)
1513afc4and73e4dc12, so PTC behavior from fix(deps): pin Lighthouse with #9959 for PTC data requests #1317 is unchanged.beacon_nodeandconsensus/{fork_choice,proto_array}. Anchor pullsproto_arrayin only as an indirect dependency and does not use that fork-choice code.Cargo.tomlandCargo.lockare unchanged between the two revs, so the mirrored[patch.crates-io]entries stay correct.Validation (Required)
git diff 1513afc4 73e4dc12in Lighthouse: no changes undercommon/eth2,validator_client, or the beacon-node validator routes; only the fork-choice files above differ.make cargo-fmt-check,make lint, andcargo nextest run --release --workspace --no-fail-fast: passed, 993 tests.Rollback (Required for behavior or runtime changes; optional otherwise)
Revert to the #1317 fork pin. No config or data impact.
Blockers / Dependencies (Optional)
anchor/unstable-9ee3fd7-pr9959branch onshane-moore/lighthousewhile any tag or release candidate builds from1513afc4.🤖 Generated with Claude Code