Skip to content

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Sep 18, 2025

Prepare Changelog for 9.1.4.

Merge once the BC that will be published is decided.


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

* docs: Close changelog for 9.1.4

* add markdown

* fix formatting

---------

Co-authored-by: elasticmachine <[email protected]>
Co-authored-by: Colleen McGinnis <[email protected]>
Co-authored-by: Eric Beahan <[email protected]>
(cherry picked from commit ecb59a5)

# Conflicts:
#	CHANGELOG.asciidoc
#	libbeat/docs/release.asciidoc
@mergify mergify bot added backport conflicts There is a conflict in the backported pull request labels Sep 18, 2025
Copy link
Contributor Author

mergify bot commented Sep 18, 2025

Cherry-pick of ecb59a5 has failed:

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

You are currently cherry-picking commit ecb59a5be.
  (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:   CHANGELOG.next.asciidoc
	modified:   docs/release-notes/index.md

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   CHANGELOG.asciidoc
	both modified:   libbeat/docs/release.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

@mergify mergify bot requested review from a team as code owners September 18, 2025 18:31
@mergify mergify bot added backport conflicts There is a conflict in the backported pull request labels Sep 18, 2025
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Sep 18, 2025
Copy link
Contributor

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

@github-actions github-actions bot added docs in progress Pull request is currently in progress. release automation Team:Automation Label for the Observability productivity team forwardport-main Automated forwardport with mergify labels Sep 18, 2025
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Sep 18, 2025
Copy link
Contributor

github-actions bot commented Sep 18, 2025

🔍 Preview links for changed docs

@colleenmcginnis colleenmcginnis enabled auto-merge (squash) September 22, 2025 16:41
Copy link
Contributor

@vishaangelova vishaangelova left a comment

Choose a reason for hiding this comment

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

LGTM!

@colleenmcginnis colleenmcginnis merged commit 9432137 into main Sep 22, 2025
14 checks passed
@colleenmcginnis colleenmcginnis deleted the mergify/bp/main/pr-46618 branch September 22, 2025 18:15
**Filebeat**

- Improve HTTP JSON health status logic for empty template results. [46332]({{beats-pull}}46332)
- Improve CEL input documentation of authentication options. [46253]({{beats-pull}}46253)
Copy link
Contributor

@vishaangelova vishaangelova Sep 22, 2025

Choose a reason for hiding this comment

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

I know this is a backport, but the changes on line 27 and 29 are only doc changes, do we/should we include doc changes in the release notes?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automation backport conflicts There is a conflict in the backported pull request docs forwardport-main Automated forwardport with mergify in progress Pull request is currently in progress. release Team:Automation Label for the Observability productivity team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants