chore: sync master → develop — publish changelog.md to GitBook (#127)

[ton77v]

Advances develop (the GitBook-published branch) up to master — the publish step of the changelog.md collapse (umbrella beshu-tech/ror-api#127).

develop is currently a clean ancestor of master (0 ahead), so this is a fast-forward — no conflicts. It brings onto develop / GitBook:

• changelog.md (ror-api's detailed render, with the generated-file disclaimer header)
• SUMMARY.md → [Changelog](changelog.md) (Phase C, chore(#128): repoint SUMMARY → changelog.md + delete detailed_changelog.md (Phase C) #322)
• removal of detailed_changelog.md (Phase C, chore(#128): repoint SUMMARY → changelog.md + delete detailed_changelog.md (Phase C) #322)

After this merges, docs.readonlyrest.com serves the changelog from changelog.md and the old detailed_changelog.md is gone — the two-overlapping-files issue Mateusz flagged is fully resolved. No manual SUMMARY edit needed.

Tip: for a true fast-forward (no merge commit) you can instead run git push origin master:develop if develop isn't push-protected. Either way publishes the same state.

🦀 sent by Claude Code

Summary by CodeRabbit

• Bug Fixes

  • Security fix for CVE-2026-42587
  • Fixed KBN tenancy-creation issues following Kibana in-place upgrades
  • Fixed DevTools authorization restrictions for Grok Debugger and Painless Lab access

• Documentation

  • Updated changelog with version 1.70.1 release information and fixes

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR updates documentation links and adds release notes. SUMMARY.md is redirected to consolidate changelog references, and changelog.md receives an auto-generation notice plus a new ROR 1.70.1 release section documenting a security fix and two bug fixes.

Changes

Changelog Documentation Updates

Layer / File(s)	Summary
TOC link redirect to consolidated changelog SUMMARY.md	The "Changelog" table-of-contents entry is updated to link to changelog.md instead of detailed_changelog.md.
Changelog content and release notes changelog.md	An auto-generation notice is added to the top of changelog.md, followed by a new ROR 1.70.1 (2026-06-12) release section with three <details> entries: one security fix (CVE-2026-42587) and two bug fixes (KBN tenancy repair after Kibana upgrades and DevTools authorization for Grok Debugger/Painless Lab access).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 The changelog hops with latest news,
A redirect guides the weary muse,
New fixes bundled, secure and sound,
Where documented truths are found.
Release notes flourish, crisp and clean! 📝

🚥 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 PR title accurately describes the main objective: syncing master to develop and publishing the changelog to GitBook as part of Phase C changes.
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 master

---

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]

Actionable comments posted: 1

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

Inline comments:
In `@changelog.md`:
- Line 5: The release heading currently uses "### (2026-06-12) What's new in
**ROR 1.70.1**" which skips an h2 and triggers lint warnings; change that
heading token from "###" to "##" so the document goes from the top-level "#
Changelog" to a proper h2 for the new release section.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: e7f70603-b365-4353-a9d4-3201b8f75c46

📥 Commits

Reviewing files that changed from the base of the PR and between e6e5b09 and b9808ad.

📒 Files selected for processing (2)

• SUMMARY.md
• changelog.md

[coderabbitai]

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Fix the heading level for the new release section.

### jumps straight from the document’s # Changelog title to an h3, which breaks the heading hierarchy and triggers the markdown lint warning. Use ## here instead.

🧰 Tools

🪛 markdownlint-cli2 (0.22.1)

[warning] 5-5: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3

(MD001, heading-increment)

🤖 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 5, The release heading currently uses "### (2026-06-12)
What's new in **ROR 1.70.1**" which skips an h2 and triggers lint warnings;
change that heading token from "###" to "##" so the document goes from the
top-level "# Changelog" to a proper h2 for the new release section.

Source: Linters/SAST tools