PR #79162 revised the breaking changes categories in the doc. Follow this by revising the categories that changelog YAML files can use.
@@ -191,33 +191,18 @@
"breakingArea": {
"type": "string",
"enum": [
- "API",
- "Aggregation",
- "Allocation",
- "Authentication",
- "CCR",
- "Cluster",
- "Discovery",
- "Engine",
- "HTTP",
- "Highlighters",
- "Indices",
- "Java",
- "License Information",
+ "Cluster and node setting",
+ "Command line tool",
+ "Index setting",
+ "JVM option",
+ "Java API",
"Logging",
- "Machine Learning",
- "Mappings",
- "Networking",
+ "Mapping",
"Packaging",
- "Plugins",
- "Script Cache",
- "Search Changes",
- "Search",
- "Security",
- "Settings",
- "Snapshot and Restore",
- "Transform",
- "Transport"
+ "Painless",
+ "REST API",
+ "System requirement",
+ "Transform"
]
},
"additionalProperties": false
@@ -5,7 +5,7 @@ type: breaking
issues: []
breaking:
title: HTTP Status code has changed for the Cluster Health API in case of a server timeout
- area: API
+ area: REST API
details: |-
The cluster health API includes options for waiting
for certain health conditions to be satisfied. If the requested conditions are