Skip to content

fix: close #4 - #5

Merged
reaatech merged 1 commit into
mainfrom
issue/ci-failing-on-main-release-4
May 19, 2026
Merged

fix: close #4#5
reaatech merged 1 commit into
mainfrom
issue/ci-failing-on-main-release-4

Conversation

@reaatech

Copy link
Copy Markdown
Owner

Summary

The fix is already applied. Two files were added — e2e/vitest.config.ts and packages/observability/vitest.config.ts — each containing a standard vitest config using defineConfig from vitest/config with globals: false, environment: 'node', and text+json-summary coverage. Without these configs, vitest 3.x's default include pattern (tests/**/*.test.js) skipped the .ts test files in both packages, causing vitest run to exit code 1 with "No test files found". With them, all 21 tasks (12 relevant tests across observability and e2e) pass.

Closes #4

The fix is already applied. Two files were added —  and  — each containing a standard vitest config using  from  with , , and text+json-summary coverage. Without these configs, vitest 3.x's default  pattern () skipped the  test files in both packages, causing  to exit code 1 with "No test files found". With them, all 21 tasks (12 relevant tests across observability and e2e) pass.
@reaatech
reaatech merged commit 0f715bf into main May 19, 2026
12 checks passed
@reaatech

Copy link
Copy Markdown
Owner Author

✅ PR Pipeline Complete

  • Scope: In scope
  • Coverage: 100%
  • CI: All checks passed
  • Merge: 0f715bf

Release to npm is handled separately by the weekly publish job; this PR will be included if it resolves a High/Critical-labelled issue.

@reaatech
reaatech deleted the issue/ci-failing-on-main-release-4 branch May 19, 2026 01:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CI failing on main: Release

1 participant