Skip to content

feat(ci): add Codecov, CodeQL, changelog enforcement, bench gating#12

Merged
SimplyLiz merged 3 commits intodevelopfrom
feature/ci-hardening
Mar 10, 2026
Merged

feat(ci): add Codecov, CodeQL, changelog enforcement, bench gating#12
SimplyLiz merged 3 commits intodevelopfrom
feature/ci-hardening

Conversation

@SimplyLiz
Copy link
Owner

Summary

  • Coverage reporting: Upload test coverage to Codecov from the Node 22 matrix run (fail_ci_if_error: false so it's non-blocking)
  • CodeQL: New workflow for static security analysis — runs on push/PR + weekly Monday scan
  • Changelog enforcement: Publish job validates that CHANGELOG.md contains an entry for the release version before proceeding
  • Bench gates on test: bench now needs: [test]; publish now needs: [audit, lint, test, bench, e2e]

Setup required

  • Add CODECOV_TOKEN repo secret (or skip — Codecov works without it on public repos, upload just won't be verified)

Test plan

  • Verify CI passes on this PR (lint, test, e2e, bench)
  • Confirm CodeQL workflow appears in Actions tab
  • Coverage upload step runs (may warn without token — expected)

- Upload coverage to Codecov from Node 22 test run
- Add CodeQL workflow for static security analysis (weekly + PR)
- Validate CHANGELOG.md entry exists before publishing a release
- Gate bench job on test passing; include bench in publish dependencies
@github-advanced-security
Copy link

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

…coverage

- Set top-level permissions to read-only, grant per-job as needed
- Add concurrency group to cancel in-progress runs on new pushes
- Add dependency-review-action on PRs (fail on high severity)
- Add vitest-coverage-report-action for PR coverage comments
- Fix CodeQL permissions (add actions: read, contents: read)
npm now authenticates via OpenID Connect using the id-token: write
permission already set on the publish job. No long-lived token needed.
@SimplyLiz SimplyLiz merged commit 636af51 into develop Mar 10, 2026
7 of 11 checks passed
@SimplyLiz SimplyLiz deleted the feature/ci-hardening branch March 10, 2026 01:55
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.

1 participant