Skip to content

Enhance testing infrastructure and optimize CI workflows - #18

Closed
marcomoi395 wants to merge 7 commits into
mainfrom
test/ci-workflow
Closed

Enhance testing infrastructure and optimize CI workflows#18
marcomoi395 wants to merge 7 commits into
mainfrom
test/ci-workflow

Conversation

@marcomoi395

Copy link
Copy Markdown
Owner

No description provided.

- Add Vitest testing infrastructure (vitest.config.ts, test/setup.ts)
- Write unit and integration tests across 4 phases (Core, Services, Handlers, Renderer)
- Migrate notion-sync tests from node:test to vitest
- Fix minor bugs in validators.ts and pexels.ts discovered during testing
- Add ignore branches for defensively unreachable code
- Achieve overall coverage above 95% threshold across Statements, Branches, Functions, and Lines
- Remove auto-release feature (release-please workflow)
- Add comprehensive CI workflow with quality gates:
  - Lockfile registry validation (PR only)
  - Dependency vulnerability review (PR only)
  - Lint, typecheck, unit tests, E2E tests
  - SHA-pinned actions with explicit permissions
- Add tag-triggered build-and-release workflow:
  - Creates draft releases on v* tags
  - Builds Linux (AppImage, deb) and Windows (NSIS) packages
  - Uploads assets to GitHub releases
- Update release-smoke workflow:
  - Inline matrix builds for manual testing
  - Remove dependency on deleted reusable workflow
  - Apply security standards (SHA pinning, timeouts)
- Delete obsolete workflows:
  - release-please.yml
  - build-release.yml
  - reusable-build-assets.yml
  - e2e-tests.yml (integrated into ci.yml)
- Update architecture documentation
Job will now continue even if Dependency graph is not enabled in repo settings
Project uses npm with package-lock.json as the source of truth.
yarn.lock was outdated and causing false security warnings in CI
(tar@7.5.7 vulnerabilities that don't exist in package-lock.json).
@marcomoi395
marcomoi395 deleted the test/ci-workflow branch July 22, 2026 10:20
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