We looked at the failing webauthn-device e2e test and found it unrelated to our lefthook bump. The 'Logout' button didn't appear within 5s after the WebAuthn authenticate step, which looks like a timing issue, and this task has a non-zero flakiness rate. We recommend rerunning it.
Self-Healing CI
Classification: Flaky task
An empty commit was automatically applied to the branch to trigger a new CI pipeline execution to resolve the flaky task.
The AI model provider was experiencing issues when this fix was generated.
Why this is not a code change:
The PR only bumps @evilmartians/lefthook from 2.1.6 to 2.1.17. This is a git-hook tooling devDependency. It doesn't touch the journey app, the e2e suite, or the WebAuthn flow.
touched_projects contains '*' only because the lockfile changed. The error output doesn't reference lefthook, any changed code, or any import.
The failure is a Playwright assertion timeout. The test expected the 'Logout' button to be visible within 5s after the authenticate step. The other test in the file passed, and the earlier steps of the failing test (register) completed. This points to a timing issue in a browser-driven virtual-authenticator flow, not a deterministic break.
The task's flakiness rate is above 0% (about 0.9%), so it is known to fail intermittently on the same code.
Removing the lefthook update would not logically fix the failure.
Because the failure is non-deterministic and doesn't depend on external service recovery, waiting wouldn't help. A rerun is the appropriate remedy. No code changes are proposed.