We looked at the failing WebAuthn e2e test and found it unrelated to our change, which only bumps the @types/node devDependency in package.json. The test timed out waiting for the 'Logout' button, and the task has a small nonzero flakiness rate, so we're treating it as flaky and expect a rerun to pass.
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 was not classified as a code change:
The PR only changes the @types/node devDependency version in package.json. This is a types-only package with no runtime effect, so it cannot alter browser behaviour in an e2e test.
The error does not reference any changed code. The failure is a Playwright timeout: after authenticating with the WebAuthn device, the test waited 5000ms for the 'Logout' button and did not find it. There is no import error, type error or missing symbol tied to the dependency bump.
The other test in the same run passed. The failure is isolated to one step of one test, which fits a timing or race issue in the browser and mock server flow rather than a deterministic break.
The task has a nonzero flakiness rate (about 1.1%), so it has been seen to fail intermittently on the same code.
Removing the @types/node bump would not logically fix this failure, so the burden of proof for code_change is not met.
Conclusion: flaky_task. A rerun is appropriate and no code changes are proposed.