🚀 Release v2.0

Release Date: November 28, 2025

💥 Breaking Changes

Token Configuration Overhaul

• github-token → copilot-token (renamed & now required)

  • The action now requires an explicit PAT with "Copilot Requests" permission
  • The default github.token does NOT have Copilot access — you must provide a PAT

• New repo-token input for separation of concerns

  • Use copilot-token for Copilot API access
  • Use repo-token for standard GitHub operations (push, PRs, etc.)
  • Defaults to github.token if not specified

MCP Configuration Changes

• MCP config no longer pre-configures GitHub MCP server by default
  • In v1.0, the GitHub MCP server was always injected into your config
  • In v2.0, you must explicitly configure MCP servers or use enable-all-github-mcp-tools: true
  • This gives users full control over their MCP setup

✨ New Features

🆕 New Inputs

🗑️ Removed Inputs

🛠️ Improvements

• Consolidated installation, configuration, and execution into a cleaner script
• Improved grouped logging for better CI readability
• Removed unnecessary git configuration step
• Prompt is now logged in its own group for visibility
• actions/setup-node upgraded from v4 → v6
• Boolean inputs now use proper true/false types

🔄 Migration Guide

Before (v1.0):

- uses: austenstone/copilot-cli@v1
  with:
    github-token: ${{ secrets.MY_PAT }}
    prompt: "Review this code"

After (v2.0):

- uses: austenstone/copilot-cli@v2
  with:
    copilot-token: ${{ secrets.COPILOT_TOKEN }}
    prompt: "Review this code"

Full Changelog: v1.0...v2.0