mirror of
https://github.com/elastic/kibana.git
synced 2025-04-23 09:19:04 -04:00
Update 8.0 breaking change template to gather information on how to programmatically detect it. (#82905)
This commit is contained in:
parent
76fd29a452
commit
729631a76d
1 changed files with 2 additions and 0 deletions
2
.github/ISSUE_TEMPLATE/v8_breaking_change.md
vendored
2
.github/ISSUE_TEMPLATE/v8_breaking_change.md
vendored
|
@ -30,6 +30,8 @@ requesting the breaking change to be surfaced in the Upgrade Assistant.
|
|||
<!-- e.g. Based on telemetry data, roughly 75% of our users will need to make changes to x. -->
|
||||
<!-- e.g. A majority of users will need to make changes to x. -->
|
||||
|
||||
**How can we programmatically determine whether the cluster is affected by this breaking change?**
|
||||
|
||||
**What can users do to address the change manually?**
|
||||
|
||||
<!-- If applicable, describe the manual migration steps and/or link to available docs. -->
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue