I maintain GIMP for Mac. I've done it since 2021, and most of the work isn't GIMP itself. It's the dependencies. So I can build for older Macs, I carry a pile of patches against upstream: GTK, and a fair bit of GNOME and freedesktop. I don't want any of them. Each one is a patch I'm waiting to delete.

The thing stopping me deleting a patch is one question: is the upstream fix released yet?

A lot of other people have the same problem, both on public repos and inside private companies. Pretty much anywhere you aren't doing full CI/CD, there's some amount of unreleased code.

In my case, someone fixes the bug in a commit (often it's me). A merge request merges. Good. But that's not a release. Until the fix ships in a tagged version my patch has to stay, because I actually pick up the fix through MacPorts.

So I have to check: did this fix make it into a release, and which one?

There's no easy way to do that on GitHub or GitLab. The web UI won't tell you. git tag --contains or git describe --contains will, after some shenanigans: clone the repo, fetch every tag, decode the output. Multiply that by a stack of projects, half of them on GitLab, and it adds up.

So I built released.

You can use it on https://released.blabberate.com, or in your terminal with your own tokens or just public access (when allowed) npx git-released <commit-or-pr>. For example:

$ npx git-released github.com/honojs/hono/commit/f82aba8
First released in  v4.12.11
          on date  2026-04-06
           commit  f82aba8
          also in  v4.12.12, v4.12.13, v4.12.14, v4.12.15, v4.12.16
        permalink  https://released.blabberate.com/r/honojs/hono/c/f82aba8

or try a permalink: https://released.blabberate.com/r/honojs/hono/c/f82aba8

Paste a commit, a SHA, or a merged PR/MR and it gives you the first release that contains it and the date it shipped, or a plain "not yet." No clone needed. It works on any public GitHub repo, and on the GitLab hosts I actually live in: GNOME, freedesktop, KDE, Debian (salsa), and more.

Two things come with every answer:

• A link you can paste into an issue or a PR. Whoever opens it sees the same answer.
• A badge. Drop it in a PR and it reads "not yet released" until the commit ships, then changes to the version on its own. I use it so I stop re-checking the same merge request.

For private repos, or if you'd rather not depend on a website, there's a CLI (npx git-released <commit-or-pr>) that uses your own token.

On the web: https://released.blabberate.com

If you maintain something, or just keep getting asked "is my fix out yet?", give it a go and tell me where it falls over. Source is on GitHub: https://github.com/lukaso/released