rinilkunhiraman/dev-pulse — explained in plain English
Analysis updated 2026-05-18
Ask what breaking changes shipped in a specific release of a tool you depend on.
Search across ten popular open source projects' release notes with one chat interface.
Study a working example of a retrieval-augmented AI agent with evaluation and monitoring built in.
| rinilkunhiraman/dev-pulse | 0xallam/my-recipe | 0xhassaan/nn-from-scratch | |
|---|---|---|---|
| Stars | 0 | — | 0 |
| Language | Python | Python | Python |
| Last pushed | — | 2022-11-22 | — |
| Maintenance | — | Dormant | — |
| Setup difficulty | moderate | moderate | moderate |
| Complexity | 4/5 | 2/5 | 4/5 |
| Audience | developer | general | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires uv, a running Ollama instance with a chat model, and about 2GB of disk space.
DevPulse is a project that lets you ask plain English questions about software release notes and get back answers that cite the exact version where a change happened. It was built as a capstone project for a course called LLM Zoomcamp. The idea addresses a real problem: developers rely on many open source tools that release updates constantly, and nobody has time to read every changelog, yet missing an important breaking change can cause problems in production. The system works by pulling release notes from the GitHub Releases page of ten popular open source projects, including Node.js, React, Next.js, Docker Compose, and TypeScript, covering close to 1,800 individual releases. Those notes are broken into chunks and indexed two ways: a traditional keyword based search and a vector search that captures meaning rather than exact words, with the two combined for better results and then reordered by a separate reranking step to surface the most relevant chunks. An AI agent built with Pydantic AI decides which project to search for a given question, can run multiple searches if needed, and always cites the specific release version behind each fact it states. A scheduled workflow refreshes this whole knowledge base automatically every week so answers stay current. The project includes a formal evaluation comparing different search methods, finding that combining keyword and vector search with reranking performed best, and comparing two different prompt styles for the AI, where a simpler prompt actually gave better answers than an overly cautious one. Every question and search is also logged with detailed tracing, feeding a built in monitoring dashboard that shows request volume, response times, token usage, estimated cost, and user feedback collected as thumbs up or down on each answer. Running the project locally requires a Python package manager called uv, plus Ollama for running the underlying language model, and involves downloading models, fetching the release data, building the search indexes, and starting a chat interface built with Streamlit. Docker Compose is also supported as an alternative way to run the whole system, including the scheduled weekly refresh job.
An AI agent that answers plain-English questions about software release notes, citing the exact version behind each fact, refreshed weekly.
Mainly Python. The stack also includes Python, Ollama, Pydantic AI.
Setup difficulty is rated moderate, with roughly 1h+ to a first successful run.
Mainly developer.
This repo across BitVibe Labs
double-check against the repo, no cap.