Skip to content

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Oct 6, 2025

Resolves #7077: adds the 8.18.8 Security and Endpoint release notes.

Preview: 8.18


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

* Security 8.18.8 release notes

* Update docs/release-notes/8.18.asciidoc

Co-authored-by: Nicholas Berlin <56366649+nicholasberlin@users.noreply.github.com>

* Update docs/release-notes/8.18.asciidoc

Co-authored-by: Nicholas Berlin <56366649+nicholasberlin@users.noreply.github.com>

* Apply suggestions from code review

Co-authored-by: Gabriel Landau <42078554+gabriellandau@users.noreply.github.com>

---------

Co-authored-by: Nicholas Berlin <56366649+nicholasberlin@users.noreply.github.com>
Co-authored-by: Gabriel Landau <42078554+gabriellandau@users.noreply.github.com>
(cherry picked from commit cef7330)

# Conflicts:
#	docs/release-notes.asciidoc
@mergify
Copy link
Contributor Author

mergify bot commented Oct 6, 2025

Cherry-pick of cef7330 has failed:

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

You are currently cherry-picking commit cef7330f.
  (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

github-actions bot commented Oct 6, 2025

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 merged commit b6db03d into 8.18 Oct 6, 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