ci: fix dependabot coverage for cargo-fuzz and console/misc/docker - #38315
Merged
Conversation
This was referenced Aug 18, 2026
Closed
Two configured directories were not actually covered, in opposite ways. `/test/cargo-fuzz` produced only unmergeable PRs. The fuzz crates reach the root workspace through `path` dependencies, so dependabot resolves that directory to the root `Cargo.toml` and edits it while owning neither the root `Cargo.lock` nor the fuzz manifests. Thirteen such PRs have opened, none merged, and no dependabot commit ever touched `src/*/fuzz/Cargo.toml`. Drop it, and say why in a comment. `check_fuzz_versions_mirror_root` in `bin/lint-cargo` still enforces the pins, tripping only on a semver-incompatible root bump. `/console/misc/docker` was added as a second `directory:` key in an existing entry, and YAML keeps only the last, so it resolved to `/misc/images/materialized-base`. Collapse the eight byte-identical docker entries into one `directories:` list rather than add a ninth. Dependabot can now group updates across docker directories into one PR. Pin that Dockerfile's builder by multi-arch index digest, matching the nginx base in the same file, so the new coverage has something stable to refresh. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
def-
force-pushed
the
dependabot-coverage-fixes
branch
from
August 18, 2026 06:37
4643c8c to
ba0961b
Compare
jasonhernandez
approved these changes
Aug 18, 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
2 participants
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.
Two configured directories were not actually covered, in opposite ways.
/test/cargo-fuzzproduced only unmergeable PRs. The fuzz crates reach the root workspace throughpathdependencies, so dependabot resolves that directory to the rootCargo.tomland edits it while owning neither the rootCargo.locknor the fuzz manifests. Thirteen such PRs have opened, none merged, and no dependabot commit ever touchedsrc/*/fuzz/Cargo.toml. Drop it, and say why in a comment.check_fuzz_versions_mirror_rootinbin/lint-cargostill enforces the pins, tripping only on a semver-incompatible root bump./console/misc/dockerwas added as a seconddirectory:key in an existing entry, and YAML keeps only the last, so it resolved to/misc/images/materialized-base. Collapse the eight byte-identical docker entries into onedirectories:list rather than add a ninth. Dependabot can now group updates across docker directories into one PR.Pin that Dockerfile's builder by multi-arch index digest, matching the nginx base in the same file, so the new coverage has something stable to refresh.