[DOCS] Adds tagged region for notable breaking changes #1271
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a tagged region in the Elasticsearch Hadoop Breaking changes page (https://www.elastic.co/guide/en/elasticsearch/hadoop/master/breaking-changes.html), such that content can be re-used in the Installation and Upgrade Guide (https://www.elastic.co/guide/en/elastic-stack/master/elastic-stack-breaking-changes.html).
At least one tagged region must exist to prevent build errors in the Installation and Upgrade Guide, though as is the case now for V8.0.0 it can be an empty tagged region.
At this time, the Installation and Upgrade Guide for version X only lists the breaking changes specific to that version. Since this Elasticsearch Hadoop page contains information about multiple versions, I've made the tagged regions version-specific (i.e. tag::notable-v8-breaking-changes[]).
Related to elastic/docs#789 and elastic/stack-docs#268