Skip to content

Releases: Hankaws/aperture-bot

v1.9

Choose a tag to compare

@github-actions github-actions released this 01 Nov 09:43

Built from Hankaws/aperture@f8a5e25. See its changelog.

v1

v1

Choose a tag to compare

@Hankaws Hankaws released this 13 Oct 16:49

The current Aperture Bot 1.x. This tag moves to each 1.x release, so uses: hankaws/aperture-bot@v1 always gets the newest one without a breaking change. Today it is the same as v1.1: see its notes for what's new.

v1.8

Choose a tag to compare

@github-actions github-actions released this 31 Oct 21:05

Built from Hankaws/aperture@5a098e2. See its changelog.

v1.7

Choose a tag to compare

@github-actions github-actions released this 31 Oct 19:05

Built from Hankaws/aperture@fa41494. See its changelog.

v1.6

Choose a tag to compare

@github-actions github-actions released this 31 Oct 13:40

Built from Hankaws/aperture@5edb59a. See its changelog.

v1.5

Choose a tag to compare

@github-actions github-actions released this 31 Oct 10:10

Built from Hankaws/aperture@26de70b. See its changelog.

v1.4

Choose a tag to compare

@Hankaws Hankaws released this 19 Oct 18:14

v1.4 — the agent can now reorganise files:

  • move_file moves or renames a file and updates every import of it.
  • New files: an edit to a path that doesn’t exist creates it. Secrets files such as .env are refused.
  • delete_file removes a file the change no longer needs, and the check fails while anything still imports it.

v1.3.1

Choose a tag to compare

@Hankaws Hankaws released this 19 Oct 10:48
Build dist from Hankaws/aperture@main

v1.3

Choose a tag to compare

@Hankaws Hankaws released this 15 Oct 07:36

Aperture Bot now works with the TypeScript compiler, the way the editor does: it finds where a name is used, renames it everywhere, and its reply says exactly which lines still depend on what it changed. Workflows on @v1 get this release too.

New

  • Find every use of a name. Before it changes a function's arguments or what it returns, the bot can ask the compiler for every place the name is used, by file and line. That includes an import under another name (import { listTasks as lt }), and it leaves out comments, docs, and unrelated code that happens to use the same name.
  • Rename everywhere. A rename goes through the compiler, as F2 does in the editor, so every use, import and re-export changes together, one edit per file. Comments and strings keep the old name.

Better

  • An exact "Elsewhere:" line. The note at the end of a reply now comes from the compiler: Elsewhere: listTasks is used in src/routes/tasks.ts (lines 2, 13), scripts/check-store.ts (lines 2, 8). It used to be a text search that named files, not lines, and could count unrelated code that used the same name.
  • A removed name that other code still uses is flagged. When a change deletes something another file still imports: Elsewhere: listTasks is gone but still used in src/routes/home.ts:1.

Built from Hankaws/aperture@8b84c01. Inputs are unchanged, so nothing in an existing workflow needs to change.

v1.2

Choose a tag to compare

@Hankaws Hankaws released this 14 Oct 16:32

A small release: Aperture Bot's replies read more plainly, and the bot is built from the same Aperture source as the site today. Workflows on @v1 get this release too.

Better
"Elsewhere:" instead of "Didn't:". The recap at the end of a reply lists other files that still use a name the change touched, so you can look at them before merging. It used to start with "Didn't:", which read like a failure. It is a note, not a failure: "Elsewhere: listTasks also appears in src/routes/tasks.ts".
Under the hood
Built from the current Aperture source, so the bot runs the same checks as the editor and Agent Check today.
The bot passes Agent Check's new baseline settings explicitly and keeps today's behavior: it recomputes the base test result on every run. Nothing to change in your workflow.
Built from Hankaws/aperture@d0191f9. Inputs are unchanged, so nothing in an existing workflow needs to change.