Skip to content

Evidrift v0.3.1

Choose a tag to compare

@github-actions github-actions released this 17 Jul 05:50
113162c

Code compiles. APIs drift.

Evidrift v0.3.1 makes the real failure path visible before asking anyone to configure a repository.

Evidrift demo: a TypeScript signature passes, changes, and fails deterministically

Try it

Run the complete PASS-to-FAIL fixture without a global install:

npx --yes evidrift@0.3.1 demo

Pin it in a repository or CI workflow:

npm install --save-dev evidrift@0.3.1
npx evidrift init

No Evidrift account, API key, cloud backend, package-code execution, or LLM judge is required.

The case this release demonstrates

A dependency changes one declaration from:

parseConfig(input: string, options?: ParseOptions): ParseResult

to:

parseConfig(input: string, options: ParseOptions): ParseResult

The existing consumer already passes options, so TypeScript still compiles. Evidrift recomputes the recorded external contract and reports the old signature, current signature, affected line, Receipt ID, and a deterministic FAIL contract_mismatch.

Read the complete, reproduced case: TypeScript compiles, but the dependency signature has drifted.

What changed in v0.3.1

  • Added a zero-install, self-contained evidrift demo path.
  • Added a real 1200×675 GIF rendered from the captured deterministic CLI transcript.
  • Added a static GitHub Pages discovery site, FAQ, llms.txt, canonical metadata, robots.txt, and sitemap.
  • Made bare invocation and evidrift init print concrete demo, agent, commit, and CI next steps.
  • Aligned CLI, npm, GitHub, and MCP Registry metadata on 0.3.1.

Verification behavior and the Receipt schema did not change in this release.

Release map

Boundary

Evidrift does not prove runtime correctness or decide whether a dependency change is good. It checks that a deterministic TypeScript or repository-local JSON contract previously recorded for an affected line still matches.