Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[8.15] [Request][8.15.4 & 8.16.0] Add RN summary about Defend bug fix (backport #6429) #6432

Open
wants to merge 1 commit into
base: 8.15
Choose a base branch
from

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Jan 16, 2025

Fixes #6428.

Previews:

* First draft

* Fixes links

* Update docs/release-notes/8.15.asciidoc

Co-authored-by: Gabriel Landau <[email protected]>

* Update docs/release-notes/8.16.asciidoc

Co-authored-by: Gabriel Landau <[email protected]>

---------

Co-authored-by: Gabriel Landau <[email protected]>
(cherry picked from commit 471a633)

# Conflicts:
#	docs/release-notes/8.16.asciidoc
@mergify mergify bot requested a review from a team as a code owner January 16, 2025 18:10
Copy link
Contributor Author

mergify bot commented Jan 16, 2025

Cherry-pick of 471a633 has failed:

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

You are currently cherry-picking commit 471a633b.
  (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.15.asciidoc

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   docs/release-notes/8.16.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

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.

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.

1 participant