Repository navigation
feat: v1.11 hardening follow up - #513
Merged
Merged
Conversation
|
KaloyanTanev
approved these changes
Oct 28, 2026
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.
Summary
Backport of #512 to
main-v1.11, plus the charon bump to v1.11.3, which redacts credentials and API keys in logged beacon node and execution URLs.charonv1.11.2 → v1.11.3 in the compose files and thescripts/editscripts. The edit e2e test keeps v1.11.2 until the image exists.Merge after charon v1.11.3 is published, otherwise
docker compose pullfails.Release note: a client version left uncommented in
.env, which was ignored until now, takes effect after upgrading.