chore(deps): Bump yaml from 2.8.2 to 2.8.3 in the production-dependencies group

[dependabot]

Bumps the production-dependencies group with 1 update: yaml.

Updates yaml from 2.8.2 to 2.8.3

Release notes

Sourced from yaml's releases.

v2.8.3

• Add trailingComma ToString option for multiline flow formatting (#670)
• Catch stack overflow during node composition (1e84ebb)

Commits

• ce14587 2.8.3
• 1e84ebb fix: Catch stack overflow during node composition
• 6b24090 ci: Include Prettier check in lint action
• 9424dee chore: Refresh lockfile
• d1aca82 Add trailingComma ToString option for multiline flow formatting (#670)
• 4321509 ci: Drop the branch filter from GitHub PR actions
• 47207d0 chore: Update docs-slate
• 5212fae chore: Update docs-slate
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[sjnims]

@dependabot rebase

[sjnims]

@dependabot rebase

[claude]

CI Failure Analysis: CI - Test

Run: #23464969514 | Commit: 07f5543

Summary

All tests passed, but the run exited with code 1 due to an unhandled EINVAL error in Vitest's HTML/UI coverage reporter. The reporter attempted to copy coverage/ into coverage/coverage/ (a subdirectory of itself), which is an invalid filesystem operation.

Failures Found

File	Line	Issue
node_modules/@vitest/ui/dist/reporter.js	181	HTMLReporter.onFinishedReportCoverage calls cp with overlapping src/dest paths

Error Details

SystemError: Invalid src or dest: cp returned EINVAL
  (cannot copy .../coverage to a subdirectory of self .../coverage/coverage)

Root Cause

The Vitest coverage configuration likely has the reportsDirectory set to ./coverage while the HTML/UI reporter is also configured to output into a subdirectory of the coverage folder. When @vitest/ui tries to copy its assets into the coverage output directory, the source and destination overlap, causing EINVAL.

This is likely triggered by the yaml dependency bump changing the resolved @vitest/ui or coverage reporter behavior, or by an existing latent config issue that became visible.

How to Fix

Check vitest.config.ts for the coverage configuration. Ensure the HTML reporter's output directory doesn't nest inside the coverage reportsDirectory. Typical fix:

// vitest.config.ts
export default defineConfig({
  test: {
    coverage: {
      reportsDirectory: './coverage',
      // Ensure no reporter outputs to a subdirectory like './coverage/coverage'
    },
  },
});

Alternatively, if using @vitest/ui, ensure its outputFile doesn't conflict:

# Reproduce locally
npm test -- --coverage

# If it passes locally, the issue may be CI-specific (e.g., leftover coverage/ dir from a prior step)
# Try adding a clean step before tests:
rm -rf coverage/
npm test -- --coverage

If the issue is a stale coverage/ directory from a prior CI step, add rm -rf coverage before the test command in the workflow.

---

Analyzed by Claude