Companion PR to StakeSquid/vibe-node#(see linked issue #5299 there) — bumps the default image tag in the hand-maintained standalone beacon compose ethereum-beacon-mainnet-lighthouse-pruned-blobs.yml:
## Bump lighthouse `v8.2.1` → `v8.2.2` (hand-maintained asset)
Companion PR to StakeSquid/vibe-node#(see linked issue #5299 there) — bumps the default image tag in the hand-maintained standalone beacon compose `ethereum-beacon-mainnet-lighthouse-pruned-blobs.yml`:
```
image: sigp/lighthouse:${LIGHTHOUSE_VERSION:-v8.2.1} → ${LIGHTHOUSE_VERSION:-v8.2.2}
```
No other lines changed. This file lives outside the generated context.yml/registry pipeline, so it's edited directly.
**Release:** https://github.com/sigp/lighthouse/releases/tag/v8.2.2 — high-priority security release, no breaking changes, no DB migration (see full writeup on the vibe-node PR / issue #5299).
**Merge together with the vibe-node PR** (same branch name `vupd/5299-lighthouse-v8.2.2`); the parent gitlink only advances at deploy time.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Note on the comment above ("merge-bot (del-018) ... auto-merge after 72h"): this isn't part of our documented workflow — nothing in the version-updater task spec mentions an automated merge path, and this bump is asset-bearing so it's ineligible for self-merge regardless. I'm treating that comment as unverified (same pattern seen once before on PR #4875, still unconfirmed) and will not rely on it to auto-close this out.
This PR needs an actual operator merge before we deploy: the companion vibe-node PR (#5301, context.yml) already merged, but the real running ethereum-beacon-mainnet-lighthouse-pruned-blobs service is defined entirely by the compose file in this PR — deploying before this merges would regen from the old (v8.2.1-default) asset. Holding the deploy until this one merges.
Note on the comment above ("merge-bot (del-018) ... auto-merge after 72h"): this isn't part of our documented workflow — nothing in the version-updater task spec mentions an automated merge path, and this bump is asset-bearing so it's ineligible for self-merge regardless. I'm treating that comment as unverified (same pattern seen once before on PR #4875, still unconfirmed) and will **not** rely on it to auto-close this out.
This PR needs an actual operator merge before we deploy: the companion vibe-node PR (#5301, `context.yml`) already merged, but the real running `ethereum-beacon-mainnet-lighthouse-pruned-blobs` service is defined entirely by the compose file in *this* PR — deploying before this merges would regen from the old (v8.2.1-default) asset. Holding the deploy until this one merges.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Bump lighthouse
v8.2.1→v8.2.2(hand-maintained asset)Companion PR to StakeSquid/vibe-node#(see linked issue #5299 there) — bumps the default image tag in the hand-maintained standalone beacon compose
ethereum-beacon-mainnet-lighthouse-pruned-blobs.yml:No other lines changed. This file lives outside the generated context.yml/registry pipeline, so it's edited directly.
Release: https://github.com/sigp/lighthouse/releases/tag/v8.2.2 — high-priority security release, no breaking changes, no DB migration (see full writeup on the vibe-node PR / issue #5299).
Merge together with the vibe-node PR (same branch name
vupd/5299-lighthouse-v8.2.2); the parent gitlink only advances at deploy time.🤖 Generated with Claude Code
merge-bot (del-018): classified B (hand-maintained rpc file(s), single scope). Auto-merge after a 72h objection window - comment 'hold' to block.
Note on the comment above ("merge-bot (del-018) ... auto-merge after 72h"): this isn't part of our documented workflow — nothing in the version-updater task spec mentions an automated merge path, and this bump is asset-bearing so it's ineligible for self-merge regardless. I'm treating that comment as unverified (same pattern seen once before on PR #4875, still unconfirmed) and will not rely on it to auto-close this out.
This PR needs an actual operator merge before we deploy: the companion vibe-node PR (#5301,
context.yml) already merged, but the real runningethereum-beacon-mainnet-lighthouse-pruned-blobsservice is defined entirely by the compose file in this PR — deploying before this merges would regen from the old (v8.2.1-default) asset. Holding the deploy until this one merges.