ping-javascript-sdk
The AI model provider reports an incident (Partially Degraded Service). Fix generation may be delayed or unavailable until it is resolved. View provider status
Failed after AAAJ Ancheta
View latest

ci(mend): add full scan option and cli integrity check

8622faf06fOpen on GitHub

Self-Healing CI

Classification: Flaky task

We looked at both failures and don't think our changes caused them. The api-report integration tests hit vitest's 5s timeout, and the journey e2e run timed out waiting for its webServer. Our PR only touches Mend CI workflows, lefthook, and the Playwright install step, so we expect a rerun to pass.

An empty commit was automatically applied to the branch to trigger a new CI pipeline execution to resolve the flaky task.

This was not classified as a code_change because neither failure points to anything the PR changed.

What the PR changes:

  • It adds Mend SAST and SCA actions and a release scan workflow.
  • It edits lefthook.yml.
  • It sets PLAYWRIGHT_HOST_PLATFORM_OVERRIDE in the setup action's Playwright install step.
  • The only touched project is forgerock-verdaccio.

@forgerock/api-report:test:

  • 49 of 51 tests passed.
  • Two integration tests failed with "Test timed out in 5000ms": 'should be a no-op on an already-clean package' and 'should handle multiple entry points'.
  • These tests run api-extractor synchronously, and the earlier tests in the same file took 2.5–5s each. A slow runner is the likely cause.
  • The task has a flakiness rate of about 7%, and its project is not touched by the PR.

@forgerock/journey-suites:e2e-ci--src/otp-register.test.ts:

  • Playwright reported "Timed out waiting 60000ms from config.webServer", which is a server startup timeout.
  • No error references changed code.
  • The Playwright install change only affects browser installation, not the web server.
  • The flakiness rate is 0%, but that comes from limited history and does not tie the failure to this PR.

No similar-failure branch was provided, and no task output was missing. No code changes are proposed, and a rerun is the appropriate action.