Repository navigation
ci(dependabot): replace token merge with strict gate - #1035
Merged
Merged
Conversation
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.
Root cause and repair
The former Dependabot pull-request workflow could request auto-merge with its write-capable
GITHUB_TOKENbefore exact-head checks completed. That merge path can suppress push CI. This PR replaces it with a read-only strict gate that verifies the six original required contexts and every applicable check on the exact Dependabot head. The active ruleset retains those six checks and adds the gate; no protection is weakened.GitHub CodeQL default setup was configured after this PR's prior head, so
CodeQLandAnalyze (actions)were missing there. The empty conventional commitci(codeql): refresh checks after default setuptriggered a new head,7f12fcd54c38d5d6e4a3aaf7e37509c4677fd78c, without changing source or adding a conflicting advanced workflow. All seven required contexts now report success on that exact head.Changed files
.github/workflows/dependabot-automerge.yml: read-only exact-head gate. No other file differs frommain.Native validation on the current PR content
mise exec -- hk check --all --slow: exit 0.mise exec -- cargo test --locked: exit 0.mise exec -- cargo test --locked --no-default-features --features comments,email_address,literals,normalization,serde,white-spaces: exit 0.rustup run 1.81.0 cargo test --locked --all-targets --no-default-features --features comments,email_address,literals,normalization,serde,white-spaces: exit 0.mise exec -- cargo build --locked: exit 0.mise exec -- cargo package --locked: exit 0.rustup run 1.81.0 cargo build --verbose --release --target thumbv6m-none-eabi, with Rustup/Cargo/tmp storage on the external Code drive: exit 0.git diff --check: exit 0.Logs:
/Volumes/Code/Sources/.dev-storage/mathematic-inc-monitor/2026-09-27T1501Z-full.DCnWlm/logs/addr-spec-rs-gate-{hk,test-default,test-features,test-msrv,build,package,no-std-build}.log.The exact-head strict-check evidence is on this PR's checks tab. The previous head lacked the GitHub Advanced Security
CodeQLsummary and Actions analysis; the current head'sCodeQL,CI,Check,MSRV,Analyze (actions),Analyze (rust), andStrict Dependabot gateare all completed/successful. Merge with the authenticated non-Actions credential only; verify the new default-branch SHA afterward. No release is requested.