https://abbreviatory.com/tags/release/ Recent content in release on Abbreviatory.com Hugo -- gohugo.io en-us Wed, 04 Nov 2026 00:00:00 +0000 https://abbreviatory.com/abbreviatory-now-reads-cargo-typescript-eslint-gradle-maven-and-npm-output/ Wed, 04 Nov 2026 00:00:00 +0000 https://abbreviatory.com/abbreviatory-now-reads-cargo-typescript-eslint-gradle-maven-and-npm-output/ After tests, the thing a coding agent reads most is a build failing. cargo build, tsc, npm install, mvn test. Until now Abbreviatory read those as logs. It found the lines with “error” in them and folded the repeats, which helped, but it didn’t know that a Rust error is six lines long and the useful part is the file and line in the middle. v0.5.0 does. It reads cargo (build, check, clippy and test), tsc in both its styles, ESLint, Gradle, Maven, npm and pnpm. https://abbreviatory.com/abbreviatory-now-tracks-new-warnings-and-runs-as-a-github-action/ Wed, 04 Nov 2026 00:00:00 +0000 https://abbreviatory.com/abbreviatory-now-tracks-new-warnings-and-runs-as-a-github-action/ Warnings pile up. A build has forty of them, everyone stopped reading them months ago, and the one that matters, the deprecation that turns into an error next quarter, arrives as number forty-one. Abbreviatory has always kept warnings in its report. Until now it didn’t say which ones were new. v0.6.0 does, behind a flag. Run with -warnings and a history, and the report compares warnings with the last run the way it already compares failures. https://abbreviatory.com/abbreviatory-0.3-gives-coding-agents-an-mcp-server-and-opens-a-browser-demo/ Mon, 19 Oct 2026 00:00:00 +0000 https://abbreviatory.com/abbreviatory-0.3-gives-coding-agents-an-mcp-server-and-opens-a-browser-demo/ Coding agents run tests all day. Every run prints thousands of lines, and the agent reads all of them, pays for all of them, and then often reads them again after a one-line change. Abbreviatory v0.3.0 lets the agent skip that. It’s now an MCP server, so an agent can ask it to run the tests and get back the short report instead: the failures with their messages, what changed since the last run, and one line when nothing did. https://abbreviatory.com/abbreviatory-0.4-reads-git-diffs-http-responses-and-directory-listings/ Mon, 19 Oct 2026 00:00:00 +0000 https://abbreviatory.com/abbreviatory-0.4-reads-git-diffs-http-responses-and-directory-listings/ Test runs and logs aren’t the only big outputs a coding agent reads. It reads diffs all day, to review what it changed. It calls APIs with curl and gets back a wall of JSON. It runs find to see what’s in a repository, and gets ten thousand paths. Abbreviatory v0.4.0 reads all three. Each one gets rules of its own, because each one has its own idea of what matters. https://abbreviatory.com/abbreviatory-0.2-tells-you-what-changed-since-the-last-test-run/ Sun, 18 Oct 2026 00:00:00 +0000 https://abbreviatory.com/abbreviatory-0.2-tells-you-what-changed-since-the-last-test-run/ The first release made one run’s output short. This one compares it with the run before. Abbreviatory v0.2.0 keeps a history per command, and every report now opens with what changed: which failures are new, which got fixed, which are still failing and for how long, and which tests are flaky. Most CI runs aren’t news. The same three tests failed yesterday and they fail today. Reading the full report again, or having a coding agent read it again, mostly confirms what everyone already knows. https://abbreviatory.com/abbreviatory-launches-as-an-open-source-tool-that-cuts-test-runs-and-logs-down-to-what-matters/ Sun, 18 Oct 2026 00:00:00 +0000 https://abbreviatory.com/abbreviatory-launches-as-an-open-source-tool-that-cuts-test-runs-and-logs-down-to-what-matters/ Abbreviatory v0.1.0 is out. It’s a small command-line tool that takes a big pile of tool output, a test run, a build log, a JSON response, and turns it into a short report that keeps the failures, errors and warnings. It’s open source under the Apache License 2.0 and comes as a single static binary for Linux, macOS and Windows. The problem is familiar to anyone who has scrolled a CI log. https://abbreviatory.com/how-abbreviatory-was-tested-against-its-four-promises/ Sun, 18 Oct 2026 00:00:00 +0000 https://abbreviatory.com/how-abbreviatory-was-tested-against-its-four-promises/ A tool that leaves things out has to be careful about what. So the testing for v0.1.0 is built around four promises, checked over and over: the report never goes over the budget, nothing important gets lost, the same input gives the same bytes, and every reference expands back to exactly the original. Every number in this post comes from the result files in the code repository, in test/results. They were recorded on October 18, 2026, at commit d0d473f, on a Linux machine with an Intel Xeon processor at 2.