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.17] Add Fleet & Agent 8.16.2 Release Notes (backport #1538) #1561

Merged
merged 2 commits into from
Dec 16, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Dec 16, 2024

This adds the 8.16.2 Fleet & Elastic Agent Release Notes:

Closes: #1528


Screenshot 2024-12-16 at 9 30 58 AM


This is an automatic backport of pull request #1538 done by [Mergify](https://mergify.com).

* Add Fleet & Agent 8.16.2 Release Notes

* touchup

* Update wolfi note

(cherry picked from commit d7a2989)

# Conflicts:
#	docs/en/ingest-management/release-notes/release-notes-8.16.asciidoc
@mergify mergify bot requested a review from a team as a code owner December 16, 2024 20:40
Copy link
Contributor Author

mergify bot commented Dec 16, 2024

Cherry-pick of d7a2989 has failed:

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

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

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

no changes added to commit (use "git add" and/or "git commit -a")

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.

@kilfoyle kilfoyle merged commit a86cd7e into 8.17 Dec 16, 2024
3 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.

1 participant