From fe6983b1994f03e9fba75645bccc5ae73f3d003e Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 17 Nov 2026 11:01:47 +0000 Subject: [PATCH] =?UTF-8?q?release:=20autter=203.13.0=20=E2=80=94=20autter?= =?UTF-8?q?=20tests:=20pull=20and=20run=20the=20tests=20Autter=20wrote=20f?= =?UTF-8?q?or=20a=20PR?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Bumps Cargo.toml and Cargo.lock to 3.13.0 and moves the `autter tests` entry into the 3.13.0 section of CHANGELOG.md. On merge, tag-release.yml tags v3.13.0 and release.yml publishes the binaries and the npm package. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01TtUpr4DEgxboQnDVB19Sp7 --- CHANGELOG.md | 9 +++++++++ Cargo.lock | 2 +- Cargo.toml | 2 +- 3 files changed, 11 insertions(+), 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 96b54a6..a13eb3d 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -9,6 +9,15 @@ This changelog is automatically generated by AI when releases are published. ## [Unreleased] +## [3.13.0] - 2026-11-17 + +### Added + +- **`autter tests`: run the tests Autter wrote for a pull request on your machine.** When a review's generated tests catch a bug, the failing test is never committed to the PR (it would turn CI red), so until now there was no way to pull it into your own environment to debug it. On the PR's branch, `autter tests run` writes the failing tests Autter kept into your checkout and runs each one with its framework's command (vitest, jest, mocha, `node --test`, pytest, `go test`, `cargo test`, rspec, phpunit) from its project directory, with `CI=true`. Fix the bug and run it again to see it pass. `autter tests list` shows what Autter wrote: which tests failed, where and why, which passed, and what could not run in its sandbox. `autter tests pull` only writes the files, and `autter tests clean` removes exactly what `pull` or `run` wrote (a file you edited stays unless `--force`). The PR is the one open from your current branch, or `--pr `; `--all` includes the passing tests and `--only ` picks one. If your checkout is not at the commit the tests were checked on, a note says so. + - The tests are model-written from the PR's code and run here with your environment, not in Autter's sandbox, so `run` asks before it runs anything (`--yes` skips the question; without a terminal it refuses; `--dry-run` prints what would run). The CLI builds each command from the test's framework and path and never executes the command string stored on the server. `pull` never overwrites a file it did not write. + - A test that ran against Autter's temporary database runs only with `--database-url `, pointing at a scratch database it may write to, and gets the same variable names Autter set. It never inherits your `DATABASE_URL`. + - `--json` prints one JSON document for scripts and coding agents (the test runner's own output goes to stderr). It uses your `autter login`; in local mode, or for a repository excluded from sharing, nothing is sent. It needs the Autter API with the generated-tests route; until that is deployed the command says so. + ## [3.12.0] - 2026-11-15 ### Fixed diff --git a/Cargo.lock b/Cargo.lock index 111d872..c1792ab 100644 --- a/Cargo.lock +++ b/Cargo.lock @@ -258,7 +258,7 @@ checksum = "c08606f8c3cbf4ce6ec8e28fb0014a2c086708fe954eaa885384a6165172e7e8" [[package]] name = "autter" -version = "3.12.0" +version = "3.13.0" dependencies = [ "autter", "base64", diff --git a/Cargo.toml b/Cargo.toml index fb35d3b..ba02a99 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -5,7 +5,7 @@ resolver = "3" [package] name = "autter" -version = "3.12.0" +version = "3.13.0" edition = "2024" default-run = "autter"