Skip to content

Breaking Change Detector #3

Breaking Change Detector

Breaking Change Detector #3

name: Breaking Change Detector
on:
schedule:
- cron: "0 13 * * 1-5"
workflow_dispatch:
permissions:
contents: read
copilot-requests: write
issues: write
pull-requests: read
jobs:
run:

Check failure on line 14 in .github/workflows/trigger-breaking-change-detector.yml

View workflow run for this annotation

GitHub Actions / Breaking Change Detector

Invalid workflow file

The workflow is not valid. .github/workflows/trigger-breaking-change-detector.yml (Line: 14, Col: 3): Error calling workflow 'elastic/ai-github-actions/.github/workflows/gh-aw-breaking-change-detector.lock.yml@v0'. The nested job 'activation' is requesting 'actions: read', but is only allowed 'actions: none'.
# Disabled 2026-07-02 — no current owner. Re-enable by removing this
# `if: false` line via a reviewed PR so the change is visible.
if: false
uses: elastic/ai-github-actions/.github/workflows/gh-aw-breaking-change-detector.lock.yml@v0
with:
additional-instructions: |
Do NOT flag changes to `conditions.kibana.version` or
`conditions.elastic.subscription` in any package's `manifest.yml`
as breaking changes. The Elastic package registry is version-aware:
when a package narrows its Kibana version constraint, users on
older Kibana versions are not broken — they continue to see and
use the latest package version compatible with their stack. The
newer version is simply not offered to them. Narrowing stack
version constraints is a normal, non-breaking operation in this
repository.