v3.6.0

A minor release with no breaking changes. npm create rag-pipeline scaffolds a working app, PineconeRetriever adds Pinecone, the main entry works in a deployed Cloudflare Worker, and the answer check raises fewer false alarms.

npm install @devilsdev/rag-pipeline-utils@^3.6.0
npm create rag-pipeline@latest my-app -- --template next   # or mastra, workers

Highlights

• Starter templates: npm create rag-pipeline (the new create-rag-pipeline package).

  • next: a Next.js app with any AI SDK model wrapped in groundingMiddleware.
  • mastra: a Mastra agent with a document-search tool, the groundedness scorer and guardrails.
  • workers: a Cloudflare Worker with streaming.

  Each answers from a folder of documents, returns its sources and a grounding check, and runs before you add an API key, returning the matching passages. CI builds and runs every starter. Starter templates

• PineconeRetriever. It uses Pinecone's REST API, so there's no client package to install.

  • Both kinds of index: document indexes (what Pinecone creates now) through the Documents API, and vector indexes through the vectors API. It reads which one from the index description.
  • Reads see your writes: they wait until the retriever's own writes are indexed, using Pinecone's log sequence numbers, so a query right after store() finds the new documents.
  • Same contract as pgvector and Qdrant, run against real indexes of both kinds.

  Pinecone

• Listed in the official MCP Registry as io.github.DevilsDev/rag-mcp-server. Each release now updates the listing.

Fixed

• The main entry in a deployed Cloudflare Worker (broken since 3.2.0). Installed from npm, import ... from "@devilsdev/rag-pipeline-utils" crashed when the Worker started, and a project without openai or @opentelemetry/api failed to bundle. The package now points Wrangler at the CommonJS build, and those optional peers no longer break a bundle. CI now also installs the packed package into a project of its own and runs a Worker from it; before, it tested a shortcut that hid the bug. On 3.2.0 to 3.5.0, import @devilsdev/rag-pipeline-utils/edge in Workers instead.

• Fewer lexical false alarms, found by the Claude benchmarks. The check now handles:

  • a negation in a clause the claim leaves out;
  • two negated clauses in a sentence;
  • reference numbers ("Document 3");
  • identifiers ("kinesin-8", compared whole);
  • month and numeric dates;
  • German, Spanish and French negation words.

  On every SciFact citation claim the check flagged, reviewed by hand, false alarms fell from 78 to 43 across five Claude models, and every real problem was still caught. The Benchmarks page compares 3.5.0 and 3.6, including the new false alarms the clause rule introduced, which are listed as known limitations.

Changed

• Grounding verdicts can change for checkAnswer, verifyCitations, CitationTracker, PostGenerationGuard and the judge's failure classification. Re-save the report you pass to rag-pipeline eval --baseline.

The scoped packages (@devilsdev/rag-core, -connectors, -eval, -guardrails), @devilsdev/rag-mcp-server and the new create-rag-pipeline are released at 3.6.0 too. Full details: CHANGELOG · Blog post