Docs: Update Elasticsearch versions
What does this MR do?
Update GitLab and Elasticsearch supported versions.
Related issues
Author's checklist
-
Consider taking the GitLab Technical Writing Fundamentals course. -
Follow the: -
Ensure that the product tier badge is added to topic's h1
. -
Request a review based on: - The documentation page's metadata.
- The associated Technical Writer.
Review checklist
Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.
-
If the content requires it, ensure the information is reviewed by a subject matter expert. - Technical writer review items:
-
Ensure docs metadata is present and up-to-date. -
Ensure the appropriate labels are added to this MR. - If relevant to this MR, ensure content topic type principles are in use, including:
-
The headings should be something you'd do a Google search for. Instead of Default behavior
, say something likeDefault behavior when you close an issue
. -
The headings (other than the page title) should be active. Instead of Configuring GDK
, say something likeConfigure GDK
. -
Any task steps should be written as a numbered list. - If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
-
-
-
Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review. -
Ensure a release milestone is set.
Merge request reports
Activity
changed milestone to %14.8
assigned to @marcia
1 Message 📖 This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge. Documentation review
The following files require a review from a technical writer:
doc/integration/elasticsearch.md
The review does not need to block merging this merge request. See the:
-
Metadata for the
*.md
files that you've changed. The first few lines of each*.md
file identify the stage and group most closely associated with your docs change. - The Technical Writer assigned for that stage and group.
- Documentation workflows for information on when to assign a merge request for review.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
🚫 Dangermentioned in merge request !79799 (merged)
- Resolved by Marcia Ramos
@JohnMcGuire can you please review/approve this MR? Tnx!
Edited by Marcia Ramos
requested review from @JohnMcGuire
- Resolved by Marcia Ramos
marked the checklist item Consider taking the GitLab Technical Writing Fundamentals course. as completed
marked the checklist item Ensure that the product tier badge is added to topic's
h1
. as completedmentioned in merge request !80448 (merged)
- Resolved by Marcia Ramos
marked the checklist item Ensure the appropriate labels are added to this MR. as completed
Setting label(s) Category:Global Search sectionenablement based on groupglobal search.
added Category:Global Search sectioncore platform labels
- Resolved by Marcia Ramos
added 154 commits
-
b39179d7...262fbf4a - 153 commits from branch
master
- 0dd35995 - Update supported elasticsearch versions
-
b39179d7...262fbf4a - 153 commits from branch
@kpaizee I spun the reviewer roulette and it picked you. Could you please review this MR for me? Thanks!
🙇 marked the checklist item Request a review based on: as completed
- Resolved by Marcia Ramos
Hi @marcia - sure, this looks like a straightforward change, approving and merging.
👍
requested review from @kpaizee
mentioned in commit 6dd69bb1
added workflowstaging-canary label
added workflowstaging label and removed workflowstaging-canary label
added workflowcanary label and removed workflowstaging label
added workflowproduction label and removed workflowcanary label
added releasedcandidate label
added releasedpublished label and removed releasedcandidate label
added devopsdata stores label and removed devopssystems label