We found that the webauthn-device e2e failure (the 'Logout' button never appearing after the WebAuthn authenticate step) also occurs on branch 860, so our tsx bump from 4.21.0 to 4.23.15 did not cause it. Because the failure already exists elsewhere, we are not proposing a fix here. It should be handled in its own PR.
Self-Healing CI
Classification: Environment state
No code changes are applicable.
The AI model provider was experiencing issues when this fix was generated.
This was not classified as a code_change, for these reasons:
The PR's only change is a tsx version bump from 4.21.0 to 4.23.15 in pnpm-workspace.yaml. Nothing in the diff touches the journey-app, the WebAuthn flow or the test file.
The failing task is @forgerock/journey-suites:e2e-ci--src/webauthn-device.test.ts. It fails at line 100 of the test, where expect(getByRole('button', { name: 'Logout' })).toBeVisible() times out after the 'Authenticate with the registered WebAuthn device' step.
The output from branch 860 shows the same error, with the same locator, line number and step. The decision process says that a failure that is also present on another branch is environment_state, because this PR did not cause it. A pre-existing break should be fixed in its own PR, not in every open PR at once.
The flakiness rate is only about 0.7%, so this is not a typical intermittent failure. The deterministic match with branch 860 is the stronger evidence.
No changes are proposed, and no code was modified.