How AI agents track programming language releases
An agent tracks language releases by calling/lang/releases, a wire that reads the PHP, PostgreSQL, kernel.org, Rust and Go announcement feeds at runtime, filtered withsrc. It costs $0.005 per call and holds a 21 day window, because these five publishers ship on schedules that differ by an order of magnitude.
/mcp. Nothing here needs an API key or a signup.
That spread is the thing to understand before wiring this into anything, because it determines what a quiet result means.
Five publishers, five different cadences
A live read of all five upstream feeds on 8 August 2026 shows how uneven the stream is. Counts below are items published inside the wire's 21 day window.
src | Publisher | Items in 21 days | What it announces |
|---|---|---|---|
kernel | kernel.org | 9 | mainline, stable and longterm kernels |
postgres | PostgreSQL | 6 | core releases plus ecosystem news |
php | PHP | 5 | branch patch releases and alphas |
rust | Rust | 1 | release posts and project announcements |
go | Go | 0 | release posts and project announcements |
kernel.org returned nine items and every one of them was inside the window. Go returned ten items and none of them were. Both feeds are healthy. They just operate on different clocks: kernel.org cuts stable and longterm points continuously, while the Go blog posts when there is something to say.
PHP shows a third pattern. Its five items included 8.4.24, 8.3.33 and 8.5.9, all announced the same day. PHP patches every supported branch in one batch, so an agent watching a single version string will see nothing for weeks and then see three releases at once.
Why an empty result is usually correct
/lang/releases returns nothing for src=go most weeks. That is the wire reporting accurately, not failing.
This matters because an agent that treats empty as an error will retry, and an agent that treats empty as "no release exists" will be right. The second reading is the correct one here, within the 21 day window and for these five publishers only. Anything older has fallen out of the window, and anything from a publisher not in the table was never in scope.
The window is 21 days rather than the 24 hours used on news wires for the same reason. A three day lookback on the Go feed would return nothing almost every time it was called, which makes the call worthless. Retention has to be longer than the publisher's quiet period or the wire cannot answer the question.
Upstream announcements are not GitHub release tags
There are two ways to learn that software shipped, and they are not interchangeable.
A GitHub release tag is created when a maintainer cuts the artifact. An upstream announcement is written when the project decides to tell people, and it carries the context: which branches got the fix, whether it is security or maintenance, what breaks. For PostgreSQL and the kernel, that narrative only exists upstream.
The tag side of the split is a separate wire covering Node, Python, Kubernetes, Rust, Go, React, PyTorch, Deno and Bun, described in how agents monitor open-source releases of their dependencies. Rust and Go appear on both, which is deliberate: the tag tells an agent a version exists, the announcement tells it what changed.
One caveat on src=postgres. The wire reads the PostgreSQL project's general news feed, so alongside core minor releases it carries community and ecosystem items. A live read returned a conference schedule and three third-party tool releases in the same six items. Filter on the version string, not on the source alone.
The call an agent makes
# discovery only, no items: browse every wire, its filters and its price claude mcp add --transport http botwire https://thebotwire.com/mcp # paid, $0.005: everything from all five publishers in the window curl -i "https://thebotwire.com/lang/releases?since=21d&limit=25" # one publisher, one branch curl -i "https://thebotwire.com/lang/releases?src=php&q=8.4&since=21d" # security patches across the whole wire curl -i "https://thebotwire.com/lang/releases?q=security&since=21d&limit=50"
Parameters are src (php, postgres, kernel, rust, go), q, since and limit (1 to 50). Search is ranked keyword matching, so a version number or a project name outperforms a phrased question. The call costs $0.005 in USDC on Base with no API key and no signup. Every route, filter and price is machine-readable at /llms-full.txt.
Platform releases from managed vendors are a different stream with a much higher volume, covered in how agents monitor cloud provider release notes.
FAQ
Does this wire cover Python, Node or Java releases?
No. The five publishers are PHP, PostgreSQL, kernel.org, Rust and Go. Python and Node appear on the separate open-source releases wire, which reads their GitHub release tags. Java, .NET, Ruby and C++ are in neither. An agent answering "what languages released this month" should name the five it actually searched rather than implying a full survey.
How does an agent tell a security release from a maintenance one?
By querying for it. PHP, PostgreSQL and the kernel all put the word in the announcement title or summary, so q=security works because the publisher wrote it, not because we inferred it. When the classification is load-bearing for a patching decision, quote the announcement, link it, and read the project's own advisory before acting.
How current is the wire?
It sits in the sparse ingest tier and is polled at most every 15 minutes, which is well inside the cadence of publishers that ship on the order of days. The observed ingest interval and last poll timestamp are published live at /health, which is the ground truth for any freshness claim.
Why not read the five RSS feeds directly?
You can, and for a single project that is often the right call. The wire earns its $0.005 when an agent needs all five behind one query grammar, with parsing, deduplication and a shared window already handled at call time. The tradeoff is laid out in RSS versus a data API for real-time agent data.
Sources
The support model behind these cadences is published by the projects themselves. PostgreSQL's versioning policy states that the project supports a major version for 5 years after its initial release, with bug and security fixes shipped in a minor release at least once every three months. That quarterly floor is why the wire holds 21 days rather than three. Item counts above come from a direct read of the five upstream feeds on 8 August 2026. Poll cadence and per-call pricing for this service are published live at thebotwire.com/health. </content> </invoke>
Related: How do AI agents monitor open-source releases of their dependencies? · How do AI agents monitor cloud provider release notes?