Skip to content

Conversation

@nastasha-solomon
Copy link
Contributor

@nastasha-solomon nastasha-solomon commented Apr 29, 2025

Description

Removes longstanding known issues that have not been fixed (and are not on the docket to be fixed) from the Security release notes.

Since it's still important for users to know about these bugs, I'll be doc'ing them as "limitations" in the manual run feature docs instead. This change has already been made to the 8.18 docs. The 8.16 and 8.17 docs are being updated via #6800.

Preview:

@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.

@nastasha-solomon nastasha-solomon marked this pull request as ready for review April 29, 2025 22:01
@nastasha-solomon nastasha-solomon requested a review from a team as a code owner April 29, 2025 22:01
Copy link
Contributor

@yctercero yctercero left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @nastasha-solomon ! LGTM.

@nkhristinin we should see if we can prioritize fixing some of these for 8.19 after bulk endpoint is done.

@mergify
Copy link
Contributor

mergify bot commented May 5, 2025

This pull request is now in conflicts. Could you fix it @nastasha-solomon? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b remove-manual-rules-kis upstream/remove-manual-rules-kis
git merge upstream/8.x
git push upstream remove-manual-rules-kis

@nastasha-solomon
Copy link
Contributor Author

Closing this since this branch is no longer viable and the feature docs have already been updated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants