Skip to content

Release RAGOps 2.0.2 - #39

Merged
thangldw merged 1 commit into
mainfrom
codex/release-2.0.2
Aug 23, 2026
Merged

Release RAGOps 2.0.2#39
thangldw merged 1 commit into
mainfrom
codex/release-2.0.2

Conversation

@thangldw

Copy link
Copy Markdown
Owner

RAGOps v2.0.2

RAGOps 2.0.2 hardens the public 2.0 release path without changing the offline evaluation contract or supported readers.

  • Adds a deterministic synthetic retrieval-poisoning Failure Zoo specimen that blocks on unsupported_citation, unsupported_claim, and forbidden_output_term.
  • Verifies the published package on checkout-free Windows and preserves the same synthetic BLOCK decision and evidence verification.
  • Adds least-privilege CodeQL scanning and protected-main release gates for Python 3.11, 3.12, 3.13, Windows, and CodeQL.
  • Adds disabled-by-default local usage evidence containing only UTC timestamp, RAGOps version, top-level command, and exit code. Arguments and paths are not recorded, and no event is sent over the network.

The credential-free flagship demo still intentionally blocks a synthetic regression: citation coverage 1.0 -> 0.5, citation precision 1.0 -> 0.5, and lexical groundedness 1.0 -> 0.6. This is reproducible synthetic evidence, not production adoption evidence.

Compatibility

  • Python 3.11 or newer.
  • Dependency-free core remains offline with zero required runtime dependencies.
  • Existing scenario 0.1/0.2 and trace 0.3/0.4 readers remain supported.
  • Existing CLI commands, exit codes, and canonical PASS, WARN, and BLOCK decisions are unchanged.
  • FastAPI/Uvicorn remain optional through ragops[api].
  • No hosted MCP connector is included; the ChatGPT package remains a skills-only plugin.

@thangldw
thangldw merged commit 72a7c79 into main Aug 23, 2026
6 checks passed
@thangldw
thangldw deleted the codex/release-2.0.2 branch August 23, 2026 15:16
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