Skip to content

v0.2.0

Choose a tag to compare

@github-actions github-actions released this 10 Jul 14:56

@handong66/evidoc-repo@0.2.0 release:notes
node scripts/release-notes.mjs

Evidoc 0.2.0 - 2026-07-10

  • Fixed false-green gates for invalid fail policies/config files, changed-source coverage in the GitHub Action, nested Markdown links, and generated pre-push baselines.
  • Hardened the Local App against DNS rebinding and cross-origin writes, added explicit deterministic safe-fix application with rescan, and exposed the shared Agent Runtime Contract in Local App and GitHub Action results.
  • Consolidated configuration, fail policy, changed-impact, frontmatter, review-log, MCP tool, and safe-fix contracts into shared implementations instead of entrypoint-specific truth.
  • Prepared synchronized 0.2.0 release artifacts with exact Action tags, version/tag verification, package README/LICENSE files, tarball identity checks, and fail-before-publish registry preflight.
  • Renamed the project from DriftGuard to Evidoc across the CLI, npm package names, .evidoc configuration directory, MCP tools, GitHub Action examples, Local App, and public documentation.
  • Added compatibility detection for pre-rename handong66/DriftGuard/packages/github-action@... workflows so existing GitHub redirect users are still recognized by doctor, setup warnings, and Local App checks instead of getting duplicate Evidoc gates.
  • Redesigned the local Web app as the bilingual Evidoc Command Center with a system folder picker, fleet health, repository cockpit, triage queue, repair console, and copyable agent prompts.
  • Fixed doctor readiness detection so source-checkout GitHub Actions workflows that run Evidoc through npm, pnpm, Yarn, Bun, or direct CLI commands count as valid Evidoc gates, without emitting packaged-action PR comment warnings or comment-only advisory fail-on warnings.
  • Hardened the release workflow so npm pack/publish steps use explicit local package paths and public tarballs include runtime dist/src plus package README/LICENSE files, but not source tests or build metadata.
  • Synchronized onboarding, architecture, and planning docs with the published npx repo-evidoc package path and current local GUI behavior.