Skip to content

Conversation

@rekmarks
Copy link
Member

@rekmarks rekmarks commented Jan 20, 2026

Summary

  • Remove per-package coverage thresholds from vitest.config.ts
    • These had become completely meaningless since we stopped running coverage in CI.
  • Add GitHub Actions workflow that runs coverage on push to main and PRs
  • Deploy HTML coverage report to GitHub Pages
  • Post PR comments with coverage diff and link to full report

Changes

  • Removed 130+ lines of per-package thresholds from vitest.config.ts
  • Deleted scripts/reset-coverage-thresholds.sh and pretest hook
  • Created .github/workflows/coverage-report.yml

Coverage Report

🤖 Generated with Claude Code


Note

Introduces CI-driven coverage and removes brittle per-package thresholds.

  • Adds coverage-report.yml workflow: downloads coverage artifact, publishes HTML to GitHub Pages on main, fetches baseline on PRs, posts coverage diff via davelosert/vitest-coverage-report-action, and comments a link to the full report
  • Wires workflow into main.yml after lint-build-test; skips on merge_group
  • Updates lint-build-test.yml to run tests with --coverage only on Node 24.x and upload the coverage/ artifact
  • Simplifies testing scripts in package.json: removes pretest hook, test:ci, and scripts/reset-coverage-thresholds.sh; keeps test as vitest run
  • Updates vitest.config.ts coverage reporters to include json-summary and removes the large per-package thresholds block

Written by Cursor Bugbot for commit 3f9517a. This will update automatically on new commits. Configure here.

rekmarks and others added 8 commits January 20, 2026 15:18
…s workflow

- Remove per-package coverage thresholds from vitest.config.ts to eliminate merge conflicts
- Add 'json-summary' reporter for coverage reporting
- Delete reset-coverage-thresholds.sh script and pretest hook
- Create coverage.yml workflow that:
  - Runs tests with coverage on PR and base branches in parallel
  - Uploads coverage as artifacts (7-day retention)
  - Posts PR comments with coverage totals and deltas using vitest-coverage-report-action
- No coverage data stored in repo, preventing conflicts while enabling trend tracking

Co-Authored-By: Claude <noreply@anthropic.com>
- Deploy HTML coverage report to GitHub Pages on push to main
- Add PR comment with link to main branch coverage report
- Fix action versions (use v4 for checkout/artifact actions)
- Use dawidd6/action-download-artifact for cross-workflow artifact download

Coverage report will be available at:
https://metamask.github.io/ocap-kernel/coverage/

Co-Authored-By: Claude <noreply@anthropic.com>
…le report workflow

- Add coverage job to lint-build-test.yml to collect coverage artifacts
- Create coverage-report.yml as reusable workflow for PR comments and GitHub Pages
- Call coverage-report from main.yml after lint-build-test
- Remove standalone coverage.yml (duplicate functionality)
- Coverage now collected as part of main CI instead of running tests twice

Coverage report will be available at:
https://metamask.github.io/ocap-kernel/coverage/

Co-Authored-By: Claude <noreply@anthropic.com>
- Remove cache save/restore steps from workflows
- Fetch baseline coverage-summary.json from gh-pages URL on PRs
- Reduce artifact retention to 7 days (only needed within workflow run)
- Simplifies to only official GitHub actions, no third-party dependencies
- Gracefully handles first run when baseline doesn't exist yet

Co-Authored-By: Claude <noreply@anthropic.com>
@rekmarks rekmarks marked this pull request as ready for review January 21, 2026 01:18
@rekmarks rekmarks requested a review from a team as a code owner January 21, 2026 01:18
@rekmarks
Copy link
Member Author

Note: The "Coverage report" job is expected to fail until the modified workflows have run on main once.

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 2 potential issues.

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.

2 participants