Skip to content

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Sep 16, 2025

Resolves #7054: adds the 8.18.7 Security and Endpoint release notes.


This is an automatic backport of pull request #7063 done by Mergify.

* 8.18.7 release notes

* apply suggestion

* remove extra space

(cherry picked from commit 1b39cf5)

# Conflicts:
#	docs/release-notes.asciidoc
@mergify mergify bot added the backport label Sep 16, 2025
@mergify mergify bot requested a review from a team as a code owner September 16, 2025 08:02
@mergify mergify bot added the conflicts label Sep 16, 2025
@mergify
Copy link
Contributor Author

mergify bot commented Sep 16, 2025

Cherry-pick of 1b39cf5 has failed:

On branch mergify/bp/8.18/pr-7063
Your branch is up to date with 'origin/8.18'.

You are currently cherry-picking commit 1b39cf5b.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   docs/release-notes/8.18.asciidoc

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   docs/release-notes.asciidoc

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@github-actions
Copy link

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.

@natasha-moore-elastic natasha-moore-elastic enabled auto-merge (squash) September 16, 2025 08:10
@natasha-moore-elastic natasha-moore-elastic merged commit f3faf14 into 8.18 Sep 16, 2025
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants