Release notes for Kibana 9.5.0

[florent-leborgne]

Write the kibana release notes for the new 9.5.0 version

TriageBot — Human needed

2026-07-08

Type: documentation

Section check:

• ❌ Problem statement / context: missing — issue body is empty
• ❌ Definition of done: missing — expected scope and completion criteria are unspecified

Ambiguity / scope notes:

• The issue body is empty. Without additional context, it is not possible to determine scope, deliverables, or acceptance criteria.

Next step: Author input needed — see comment below for specific questions.

Generated by Gh Aw Issue Triage for issue #7284 · 37.1 AIC · ⌖ 8.81 AIC · ⊞ 9.1K · ◷

[github-actions]

Elastic Docs AI Menu

Check one box to run an AI workflow for this issue.

• Triage (docs-triage). Status: completed. View progress.
• Size the work (docs-size). Status: not started.
• Scope the docs work (docs-issue-scope). Status: not started.

Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

[github-actions]

✅ TriageBot finished. https://github.com/elastic/docs-content/actions/runs/28943515207

[github-actions]

@florent-leborgne the issue body is empty, so TriageBot can't determine scope or acceptance criteria. Could you add a description covering:

1. What should the Kibana 9.5.0 release notes cover? (specific features, areas, or a link to a tracking list)
2. Is this a meta/tracking issue coordinating other release notes tasks (e.g., the individual feature issues like Kibana UI language now follows the browser preference on all deployment types #7280–Configure a frozen phase from the Streams data retention page #7283), or a standalone docs task?
3. Definition of done — what does "complete" look like? (e.g., draft written, reviewed, published to elastic.co)

Generated by Gh Aw Issue Triage for issue #7284 · 37.1 AIC · ⌖ 8.81 AIC · ⊞ 9.1K · ◷