[breaking-change] Undocumented breaking changes detected (2026-03-02)

[github-actions]

Recent commits introduced a breaking change to a reusable workflow path that appears undocumented.

Breaking Changes

1. Reusable workflow path rename removed prior @v0 entrypoint

Commit(s): 2462829, previous contract introduced in 19791b2
PR: No PR found for sha:2462829 (direct commit); prior introduction was #516
What broke: Downstream callers using uses: elastic/ai-github-actions/.github/workflows/internal-gemini-cli.lock.yml@v0 now fail because that workflow file path was renamed and the old file no longer exists.
Evidence:

• Commit 2462829 renames .github/workflows/internal-gemini-cli.lock.yml -> .github/workflows/gh-aw-internal-gemini-cli.lock.yml.
• Same commit updates consumer-facing example from old path to new path in gh-agent-workflows/internal-gemini-cli/example.yml line 18.
• Current repo has only .github/workflows/gh-aw-internal-gemini-cli.lock.yml; no compatibility copy at the old path.
  Why undocumented:
• docs/upgrading.md breaking-change rename list does not include this internal-gemini-cli rename (see lines 33-38 list).
• No corresponding PR description/discussion for 2462829 with migration guidance.
• No mention found in README.md, DEVELOPING.md, or RELEASE.md.
  Suggested fix: Add explicit migration guidance (old -> new path) in docs/upgrading.md and release notes, or restore a temporary compatibility copy at the old workflow path.

Suggested Actions

• Document this workflow path break and migration in upgrade/release docs
• Consider adding a compatibility workflow copy at the old path for one release cycle

---

What is this? | From workflow: Breaking Change Detector

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

• expires on Mar 9, 2026, 1:40 PM UTC

[github-actions]

This issue was automatically closed because it expired on 2026-03-09T13:40:25.978Z.

Closed by Workflow