Repository navigation
images: stable client and security bumps for v1.11.2 - #506
Merged
Merged
Conversation
Mainnet-safe patch on the 1.11 charon line (charon stays v1.11.2): every client moves to its latest stable release, picking up this week's security fixes (Lighthouse v8.3.1 for the eMudhra CA compromise, Nethermind 2.2.0 with the October .NET servicing release, patched Go builds) without Charon v2 or any release candidate. Gloas code in these releases is inactive on mainnet. Lighthouse v8.3.1, Teku 26.10.1, Lodestar v1.50.0, Prysm v7.3.0, Nimbus v26.10.1, Nethermind 2.2.0, Reth v2.8.0, Commit-Boost v0.11.0; Prometheus v3.15.1, Grafana 13.2.4, Loki 3.7.9, Tempo 2.10.10, Alloy v1.21.1, cAdvisor v0.60.6, and prom/node-exporter v1.12.1 instead of the deprecated bitnamilegacy image. The stack's Nethermind flags are unaffected by 2.x breaking changes (JsonRpc.Host is the explicit 0.0.0.0).
|
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.
Mainnet-safe patch on the 1.11 charon line (charon stays v1.11.2): every client moves to its latest stable release, picking up this week's security fixes (Lighthouse v8.3.1 for the eMudhra CA compromise, Nethermind 2.2.0 with the October .NET servicing release, patched Go builds) without Charon v2 or any release candidate. Gloas code in these releases is inactive on mainnet.
Lighthouse v8.3.1, Teku 26.10.1, Lodestar v1.50.0, Prysm v7.3.0, Nimbus v26.10.1, Nethermind 2.2.0, Reth v2.8.0, Commit-Boost v0.11.0; Prometheus v3.15.1, Grafana 13.2.4, Loki 3.7.9, Tempo 2.10.10, Alloy v1.21.1, cAdvisor v0.60.6, and prom/node-exporter v1.12.1 instead of the deprecated bitnamilegacy image. The stack's Nethermind flags are unaffected by 2.x breaking changes (JsonRpc.Host is the explicit 0.0.0.0).