build(deps): bump actions/checkout from 6.0.2 to 7.0.0 in the actions group across 1 directory - #172
Merged
Merged
Conversation
Bumps the actions group with 1 update in the / directory: [actions/checkout](https://github.com/actions/checkout). Updates `actions/checkout` from 6.0.2 to 7.0.0 - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@de0fac2...9c091bb) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: 6.0.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: actions ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/github_actions/actions-6a98abd9ac
branch
from
July 1, 2026 21:55
f46b4ed to
5e97e11
Compare
barnabasbusa
pushed a commit
that referenced
this pull request
Aug 3, 2026
#180) Backports the generic improvements that ran ahead in `glamsterdam-devnets` and `bal-devnets` but never made it back here. Most of the earlier drift has already landed on master (coredevs SSH rosters, buildoor, the IPv6 rework, `sync_mapping`, the template-name guard, inventory-path derivation) — this is what was left. The buildoor gap below is a bug found while auditing rather than a straight copy. ## buildoor only covered 3 of 5 consensus clients `buildoor` wins on group precedence via `ansible_group_priority=100`, so any client whose args it does **not** re-merge silently loses that client's own args — bootnodes included. Only prysm, lighthouse and lodestar were re-merged, which left teku and grandine buildoor nodes unusable. Split teku/grandine into `*_container_command_extra_simple_args` (the pattern the other three already use), added their merge entries, and gave every client its subscribe-all-subnets flag — a builder has to see every attestation subnet to value a payload correctly. Every flag was verified against the real binaries rather than trusted from the source repo: | Client | Flags | Verified against | |---|---|---| | teku | `--Xfork-choice-updated-always-send-payload-attributes=true`, `--p2p-subscribe-all-subnets-enabled` | `consensys/teku:latest` (the first is a hidden `X` option, probed by running it) | | grandine | `--features=AlwaysPrepareExecutionPayload`, `--subscribe-all-subnets` | `ethpandaops/grandine:develop` (also confirmed repeated `--features` both parse) | | lighthouse | `--always-prepare-payload`, `--subscribe-all-subnets`, `--import-all-attestations` | `beacon_node/src/cli.rs` | | prysm | `--prepare-all-payloads`, `--subscribe-all-subnets`, `--p2p-colocation-whitelist` | `cmd/flags.go`, `config/features/flags.go` | | lodestar | `--emitPayloadAttributes`, `--subscribeAllSubnets` | already live on glamsterdam-devnet-7 | ## The rest - **mitogen 0.3.43 → 0.3.49** (`ansible.cfg` + `install_dependencies.sh` in lockstep) - **CI: install python build headers** — asdf compiles python from source and the runner image lacks `libbz2`/`readline`/`lzma`, so the build silently drops those modules and pip fails later - **`noqa` syntax** — `#noqa rule` is not recognised by ansible-lint; it needs `# noqa: rule` - **prysm colocation whitelist** — devnet peers are few and often share a /24, which prysm's colocation limit treats as a sybil cluster and refuses to peer with - **Skip DigitalOcean VPCs on hetzner-only devnets** (from bal-devnets) — an empty VPC per region is still billable surface and blocks project teardown - **`run.zsh`: `check_deps` and `send_funds`** — `check_deps` reports every missing tool with an install hint instead of dying on the first one mid-run ## Deliberately not included - **`validator_keys_container_name`** for teku/nimbus/grandine. It only exists in the unmerged ethpandaops/ansible-collection-general#562, so adding it now would ship a variable no released role reads. Worth a follow-up once that merges. - **Hetzner capacity-aware placement / cpx defaults** — already proposed in #166 and live on glamsterdam; not duplicated here. - **`actions/checkout` bump** — dependabot owned that in #172, now merged and pulled in here via master. - **Prefixing the remote terraform state key** — dropped at qu0b's request; the key is set per-devnet during fork setup anyway. ## Verification - `ansible-lint playbook.yaml --profile production` (the exact CI invocation) — passes - `terraform fmt -check` and `terraform validate` — clean - `zsh -n scripts/run.zsh`, plus `run.zsh check_deps` and `run.zsh help` executed - Jinja render check on all five buildoor merge expressions, confirming each client's base args survive the merge: ``` prysm -> ['--a', '--bootstrap-node=enr:x', '--prepare-all-payloads', '--subscribe-all-subnets'] lighthouse -> ['--b', '--always-prepare-payload', '--subscribe-all-subnets', '--import-all-attestations'] lodestar -> ['--c', '--emitPayloadAttributes', '--subscribeAllSubnets'] teku -> ['--d', '--Xfork-choice-updated-always-send-payload-attributes=true', '--p2p-subscribe-all-subnets-enabled'] grandine -> ['--e', '--features=AlwaysPrepareExecutionPayload', '--subscribe-all-subnets'] ```
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
1 participant
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.
Bumps the actions group with 1 update in the / directory: actions/checkout.
Updates
actions/checkoutfrom 6.0.2 to 7.0.0Release notes
Sourced from actions/checkout's releases.
Changelog
Sourced from actions/checkout's changelog.
... (truncated)
Commits
9c091bbupdate error wording (#2467)1044a6dgetting ready for checkout v7 release (#2464)f028218Bump the minor-npm-dependencies group across 1 directory with 3 updates (#2462)d914b26upgrade module to esm and update dependencies (#2463)537c7efBump@actions/coreand@actions/tool-cacheand Remove uuid (#2459)130a169Bump js-yaml from 4.1.0 to 4.2.0 (#2461)7d09575Bump flatted from 3.3.1 to 3.4.2 (#2460)0f9f3aaBump actions/publish-immutable-action (#2458)f9e715ablock checking out fork pr for pull_request_target and workflow_run (#2454)df4cb1cUpdate changelog for v6.0.3 (#2446)