We looked at the failing WebAuthn e2e test and don't think our dependency bump caused it. The PR only updates the @changesets/cli devDependency, which doesn't touch journey-app or the WebAuthn flow, and the 'Logout' button timeout looks like an intermittent timing flake. We recommend rerunning the task.
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 failure was not classified as a code_change for these reasons:
The failing task is the Playwright e2e
webauthn-device.test.ts. One test passed and one failed at line 100. There,expect(getByRole('button', {name: 'Logout'})).toBeVisible()timed out after 5000ms following the authenticate step.The PR only updates
@changesets/clifrom 3.0.2 to 3.0.3. This is a release-tooling devDependency and is not part of the journey-app, the SDK runtime, or the e2e flow.touched_projectscontains '*' only because of the lockfile change.The error references no changed code. No import, build or type error appears. Nothing in the diff can be tied to the missing Logout button.
The similar-failure subagent confirmed the failure does not appear on branch 729, so it is not a known pre-existing break on another branch.
The task's flakiness rate is non-zero (about 0.6%). That fits an intermittent timing issue in a browser-driven WebAuthn flow with a short 5s assertion timeout.
No code change is warranted, and a rerun is the appropriate action.