We looked at the failing webauthn-device e2e test. It timed out after 5s waiting for the Logout button, and this PR only bumps the build-time @microsoft/api-extractor dependency. We think this is a flaky test and suggest rerunning it, with no code changes needed.
Failed after Nnx-cloud[bot]View latest
chore(deps): update dependency @microsoft/api-extractor to v7.59.4 [Self-Healing CI Rerun]
855494bcb8Open on GitHubSelf-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 updates the dev dependency @microsoft/api-extractor from 7.58.2 to 7.59.4. This tool generates d.ts rollups at build time. It does not change runtime behavior in the journey-app or the e2e flow.
The failure is a Playwright timeout. In webauthn-device.test.ts at line 100,
expect(getByRole('button', { name: 'Logout' })).toBeVisible()timed out after 5000ms following the WebAuthn authenticate step. One test in the file passed and one failed. This is a timing problem in a browser-driven flow. The error does not reference any function, import, or file touched by the PR.The task's flakiness rate is about 1.4%, which is above 0%. That shows the task can fail intermittently on the same code.
The task output was present, so the missing-output bail-out did not apply. No similar-failure branch was provided. Nothing in the evidence links the failure to the dependency bump.
Conclusion: the failure is non-deterministic, so it is classified as flaky_task. A rerun is the appropriate response, and no code change is proposed.