AI-assisted GitHub pull request to release lookup

By Duk Hwan Kim

Works with

Try this example in Tines 3B

A workflow that identifies which GitHub release version a specific code change or fix first shipped in, starting from a plain-language description rather than a PR number. It uses LLM-powered search to find and rank matching merged pull requests, then walks the repository's release history to pinpoint the first version containing that change. Built for support teams, release managers, and engineers who need to trace features or fixes to specific versions quickly.

The problem

Finding out which software version includes a bug fix or feature often means manually checking GitHub pull requests, release tags, and commit histories. A merged pull request doesn’t necessarily mean a change has shipped, and backports across maintenance branches make the answer harder to trace.

Engineering, support, and product teams need a straightforward way to answer “Which release includes this change?” without repeatedly asking developers to investigate or knowing the exact pull request number.

Solution and impact

This workflow provides a self-service web app for tracing GitHub pull requests to software releases. Users can paste a pull request URL or number, or describe a change in plain language. Anthropic Claude turns descriptions into GitHub search queries and ranks matching merged pull requests, helping users find changes without knowing their exact titles. The workflow then checks release and commit history to identify the first containing main-line release and likely backports, with links to GitHub for verification. A scheduled refresh updates the release-history cache every ten minutes by default, while saved lookup results reduce repeated requests. GitHub data is read without modifying pull requests, releases, or repository content.

By bringing pull request search and release lookup into one interface, the workflow helps reduce manual research across tags, commits, and release pages. Support teams can find the release associated with a fix before communicating availability to customers, while engineering and product teams gain a clearer view of changes across main-line and maintenance releases. Self-service lookups help reduce interruptions for developers, and plain-language search makes repository history more accessible to colleagues who don’t know the pull request number.