You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PR #557 was merged into alpha at 2026-08-25T06:08:39Z while both workflow runs had a failing aggregate CI gate. The checks visible on the merged PR show:
generate-test-report: failed because test-reports/python-keepkey/junit.xml did not exist
both ARM firmware build jobs: skipped
both emulator build jobs: skipped
both firmware unit-test jobs: skipped
both Python integration-test jobs: skipped
both Python dylib-test jobs: skipped
Lint, crypto tests, submodule checks, and static analysis passed, but those are not substitutes for compiling the changed firmware or running its unit/integration suites. The merge also landed without the requested boundary regressions for #550 and #553 (Solana 33/256-account fail-closed cases and Ripple 1e17 boundary/serializer-FSM agreement).
This is a release-process security defect, not merely a red badge: changes to signing and parser boundaries reached alpha without any CI evidence that the firmware builds or that those paths work.
Configure alpha protection/rulesets so the aggregate CI gate is required and applies to repository owners/administrators; a red or skipped required gate must prevent merge.
Make test-report generation depend on successful evidence-producing jobs/artifact download; a report job must not run without JUnit and then mask the underlying skipped tests.
Security/release-gate defect
PR #557 was merged into
alphaat 2026-08-25T06:08:39Z while both workflow runs had a failing aggregateCI gate. The checks visible on the merged PR show:secret-scan: failed (the repo-wide baseline tracked in secret-scan blocked repo-wide: git history contains unrelated keepkey-vault/keepkey-sdk content (42 gitleaks findings, needs human secret-safety review) #544)generate-test-report: failed becausetest-reports/python-keepkey/junit.xmldid not existLint, crypto tests, submodule checks, and static analysis passed, but those are not substitutes for compiling the changed firmware or running its unit/integration suites. The merge also landed without the requested boundary regressions for #550 and #553 (Solana 33/256-account fail-closed cases and Ripple 1e17 boundary/serializer-FSM agreement).
This is a release-process security defect, not merely a red badge: changes to signing and parser boundaries reached
alphawithout any CI evidence that the firmware builds or that those paths work.Evidence:
858dfff056c8e643fb34dbebe8fd7b6ae424ebd3Required remediation
alphaprotection/rulesets so the aggregate CI gate is required and applies to repository owners/administrators; a red or skipped required gate must prevent merge.alphacan accept a PR while the aggregate CI gate is red.