From 6efa820311d91a0c312933bb62f4aab03d73e65e Mon Sep 17 00:00:00 2001 From: Matthew Mellor Date: Wed, 6 May 2026 10:30:30 -0500 Subject: [PATCH] docs(standards): correct timeline + language count in v1.10 blog post MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The post claimed "for the first eighteen months of DevRail" — DevRail's MVP closed 2026-03-08, so the project is two months old, not eighteen. The same paragraph also listed "eight core ecosystems" but enumerated ten (Python, Bash, Terraform, Ansible, Ruby, Go, JavaScript/TypeScript, Rust, Swift, Kotlin). Reframe to "Up to now ... through the ten core ecosystems we shipped from MVP through v1.9". Co-Authored-By: Claude Opus 4.7 (1M context) --- content/blog/2026-05-05-plugin-architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/blog/2026-05-05-plugin-architecture.md b/content/blog/2026-05-05-plugin-architecture.md index 8853eb3..8fd5c05 100644 --- a/content/blog/2026-05-05-plugin-architecture.md +++ b/content/blog/2026-05-05-plugin-architecture.md @@ -4,7 +4,7 @@ date: 2026-05-05 description: "DevRail v1.10 introduces a plugin architecture so anyone can ship a new language or tool integration without forking dev-toolchain. Loader, lockfile, extended-image build, and execution dispatch all in one container, one make check." --- -For the first eighteen months of DevRail, every new language meant a PR against `dev-toolchain` -- a Dockerfile change, an install script, Makefile blocks for `_lint` / `_format` / `_test` / `_security`, a standards doc, and a release. That worked while we were stabilizing the eight core ecosystems (Python, Bash, Terraform, Ansible, Ruby, Go, JavaScript/TypeScript, Rust, and most recently Swift and Kotlin), but it doesn't scale to the long tail of languages and tools real teams use. +Up to now, every new language in DevRail has meant a PR against `dev-toolchain` -- a Dockerfile change, an install script, Makefile blocks for `_lint` / `_format` / `_test` / `_security`, a standards doc, and a release. That worked through the ten core ecosystems we shipped from MVP through v1.9 (Python, Bash, Terraform, Ansible, Ruby, Go, JavaScript/TypeScript, Rust, Swift, and Kotlin), but it doesn't scale to the long tail of languages and tools real teams use. **v1.10.6 ships a plugin architecture.** Anyone can now publish a `devrail-plugin-` git repo, and any DevRail-managed project can declare it in `.devrail.yml` and pick up new tools at the next `make check`. No fork, no PR, no waiting on a release. The "one container, one make check" guarantee holds throughout.