Skip to content

v0.30.0

Latest

Choose a tag to compare

@github-actions github-actions released this 17 Nov 15:44
Immutable release. Only release title and notes can be modified.

What's new

  • Rules files for Cursor, GitHub Copilot and Windsurf are measured like CLAUDE.md. .cursor/rules/*.mdc, .cursorrules, .github/copilot-instructions.md, .github/instructions/*.instructions.md, .windsurfrules and .windsurf/rules/*.md run through the same with, without and same-length fake comparison. The model gets the text the editor would send. A rules file is read the way Claude reads it here; this does not reproduce each editor's own model or behaviour.

  • A pull request check you can copy in one file. examples/workflows/driftproof-pr.yml runs on any pull request. It finds changed skills and rules files that have test cases beside them, measures each one, and posts one table as a single comment, which it updates on later pushes. Explicit mode needs each requested provider's API key and never falls back to a subscription login. The Action's default model is now claude-haiku-5-5.

  • Badges for every skill we measured. Each published skill has a latest badge and one per model, with paste-ready README snippets, at /badges/. A badge states the reading, the model and the date. A skill that did not beat the fake says "did not beat the fake".

  • The free offer takes rules files too. At /measure/ you can send a public Cursor, Copilot or Windsurf rules file, alone or in a pack with skills, for the same three-task, two-model comparison.

  • /driftproof:measure in the Claude Code plugin opens the free offer's form on GitHub, filled in from your skill folder. Nothing is sent until you submit it.

  • The paper is now version 2, with its own DOI (10.5281/zenodo.24136677), at /paper/.

  • A receipt that fails its seal or schema shows no figure and no verdict on its page, instead of stopping the site build.

  • PR 839: test(838): spec 312 badge-gate check after issue 835

Known open

  • The pull request check recognises its own comment by asking GitHub which account its token belongs to. That is tested against recorded GitHub responses, not yet on a live repository. If GitHub answers differently, the check posts a notice instead of a comment; the job itself does not fail.
  • Two calls of the check in one workflow through a reusable workflow share one comment unless each sets comment-id.
  • The copyable workflow pins this release; the release train moves that pin with each release.