v1.2.0

✨ Remote install — adopt Aido with one file

Aido can now be installed by pinning a release tag instead of copying ~30 files (#52). Commit a single thin workflow:

jobs:
  aido:
    uses: aido-dev/aido/.github/workflows/aido-dispatch.yml@v1.2.0
    with:
      aido_ref: v1.2.0
    secrets:
      CHATGPT_API_KEY: ${{ secrets.CHATGPT_API_KEY }}
      GEMINI_API_KEY: ${{ secrets.GEMINI_API_KEY }}
      CLAUDE_API_KEY: ${{ secrets.CLAUDE_API_KEY }}

• Runs entirely in your repository's context — your event, your GITHUB_TOKEN, your secrets; Aido gets no access beyond what your workflow grants.
• Customize without copying scripts: any aido-*-config.json you add under .github/scripts/<command>/ overrides the shipped defaults.
• Upgrading is a one-line tag bump. Copy-based installs keep working unchanged.
• Full setup guide and remote-vs-copy trade-offs: examples/remote/

🐛 Bug fix — PR commenting permissions

Restored pull-requests: write on aido-summarize, aido-explain, aido-docs, aido-suggest, and aido-test workflows. A v1.0.7-era permission tightening (#42) had reduced them to read, which GitHub rejects when posting a comment on a pull request — these five commands were unable to post results since then.

⚠️ Copy-based adopters: re-copy these five workflow files (or change pull-requests: read to write in your copies).

🧪 Testing

New label-gated remote-smoke.yml workflow: adding the remote-smoke label to a PR runs an end-to-end remote-install test (remote workflow resolution → aido checkout at ref → config overlay → real comment posted). It caught the permissions regression on its first run.

Full changelog: https://github.com/aido-dev/aido/blob/main/CHANGELOG.md