[RORDEV-2040] kibana 9.4.1 support

[Dzuming]

Summary by CodeRabbit

• Documentation
  • Updated ROR 1.69.1 release documentation to reflect support for version 9.4.1 for both Kibana and Elasticsearch components.

[coderabbitai]

📝 Walkthrough

Walkthrough

Changelog documentation for ROR 1.69.1 is updated to add version 9.4.1 to the supported Kibana and Elasticsearch version lists. Changes are applied consistently across both the markdown changelog and the YAML changelog data file.

Changes

Version Support Update for ROR 1.69.1

Layer / File(s)	Summary
Add 9.4.1 to supported versions changelog.md, changelog/1.69.1.yaml	Changelog entries updated to include Elasticsearch/Kibana 9.4.1 in the supported version lists for the 1.69.1 release across both markdown and YAML formats.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• beshu-tech/readonlyrest-docs#269: Both PRs update the changelog.md "support"/"New" bullet lists to add additional supported Kibana/Elasticsearch versions.
• beshu-tech/readonlyrest-docs#245: Both PRs modify changelog support entries to update the supported version lists for KBN and ES.

Poem

🐰 A rabbit hops through version lands,
With 9.4.1 in eager hands,
Changelog entries now aligned,
Support and sparkle intertwined! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: adding Kibana 9.4.1 support to the changelog, which is reflected in both modified files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch RORDEV-2040-kibana-9.4.1-support

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

changelog.md (1)

3-3: ⚠️ Potential issue | 🔴 Critical

Remove manual edits to changelog.md — this file is auto-generated from YAML.

The render_changelog.yml workflow regenerates changelog.md from the changelog/**.yaml files whenever changes are pushed to master. Any manual edits to the markdown file will be overwritten on merge.

Keep your edits to changelog/1.69.1.yaml only. The workflow will automatically regenerate changelog.md from your YAML changes.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@changelog.md` at line 3, The changelog.md file is auto-generated and should
not be edited manually; revert any manual changes in changelog.md and instead
make your release notes in the corresponding YAML (e.g., changelog/1.69.1.yaml),
then let the render_changelog.yml workflow regenerate changelog.md on merge to
master; ensure no content edits remain in changelog.md so the CI workflow can
produce the authoritative markdown from the YAML source.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Outside diff comments:
In `@changelog.md`:
- Line 3: The changelog.md file is auto-generated and should not be edited
manually; revert any manual changes in changelog.md and instead make your
release notes in the corresponding YAML (e.g., changelog/1.69.1.yaml), then let
the render_changelog.yml workflow regenerate changelog.md on merge to master;
ensure no content edits remain in changelog.md so the CI workflow can produce
the authoritative markdown from the YAML source.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 3dbfb886-3430-46e1-afdf-9d0431ef74cb

📥 Commits

Reviewing files that changed from the base of the PR and between b548452 and 603a89d.

📒 Files selected for processing (3)

• changelog.md
• changelog/1.69.1.yaml
• detailed_changelog.md