trelix v3.2.2 to v3.3.8: A GitHub App Already Hardened and Running in Production, and a Connector That Never Touches a Pixel
docker run --entrypoint trelix-mcp ghcr.io/sairam0424/trelix:3.2.1 --help returns exit code 127: command not found. Not a typo, not a stale tag — the published 3.2.1 image never contained trelix-mcp at all. The builder stage copied core trelix and nothing else, and .dockerignore 's blanket packages/ exclusion would have blocked the MCP package even if someone had remembered the COPY line. A…
The article discusses the evolution of the GitHub app Trelix from version 3.2.2 to the current version 3.3.8. In version 3.2.2, two defects were discovered: one where the trelix-mcp command was not present in the 3.2.1 image and another where the MCP console script ignored all flags. These defects were found by running the actual published artifacts instead of the source code.
Version 3.2.3 introduced changes to address these defects by creating a CI pipeline that runs Trelix-MCP as an actual OS process talking real stdio JSON-RPC. Version 3.2.3 also fixed a bug related to LIKE -wildcard escaping in path_filter -scoped BM25/grep queries.
The bulk of the changes in this span involve a system that prevents the class of defects previously present from reaching a tag again. In version 3.3.8, the current release, the code is found to be correct, whereas previously the code had lied to the tests. The article also mentions other new features and fixes, such as a diagram connector, MCP protocol upgrade, retriever-caching fix, compression provider, audit-log pruning mechanism, and a renamed class with incorrect changelog entries.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
