We looked at the failing webauthn-device e2e test, where the Logout button is not visible after the WebAuthn authenticate step. Our check found the identical failure on branch 729, so it was not introduced by this @changesets/cli bump and we are not proposing changes in this PR.
Self-Healing CI
Classification: Environment state
No code changes are applicable.
Why this is not a code change:
The failing task is @forgerock/journey-suites:e2e-ci--src/webauthn-device.test.ts. The Playwright assertion at line 100 times out after 5000ms waiting for the 'Logout' button following the WebAuthn authenticate step.
The PR only bumps @changesets/cli from 3.0.2 to 3.0.3. This is release-tooling and has no connection to the journey app, the WebAuthn flow or the e2e test. The PR diff tool returned no changed files.
The similar-failure detector found the identical failure on branch 729: same test, same locator, same line (100) and same 5000ms timeout. The only difference was run duration (49.3s vs 49.9s).
Under the decision process, a failure that also appears on another branch is environment_state, even if the underlying cause is a real bug. It should be fixed in its own PR rather than in this dependency bump.
The task's flakiness rate is about 0.6%, which does not point to this PR as the cause.
No code changes are proposed.