Skip to content

docs: promote Supporting Services to GA and fix mkdocs warnings#375

Merged
mmols merged 1 commit intomainfrom
docs/PLAT-570/sup-services-beta-update
May 1, 2026
Merged

docs: promote Supporting Services to GA and fix mkdocs warnings#375
mmols merged 1 commit intomainfrom
docs/PLAT-570/sup-services-beta-update

Conversation

@mmols
Copy link
Copy Markdown
Member

@mmols mmols commented May 1, 2026

Summary

  • Remove "(Beta)" label from Supporting Services nav and heading
  • Add pgEdge RAG Server, PostgREST, cluster tests, and supporting
    service dev guide to mkdocs nav
  • Remove manual TOC from running-locally.md that had broken anchors
  • Add note that Supporting Services are not yet available on systemd
  • Rename "supported service" to "supporting service" in dev guide
  • Add changelog entry for Supporting Services promotion

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 1, 2026

📝 Walkthrough

Walkthrough

This PR promotes Supporting Services from beta status to generally available. Documentation is updated to reflect the new terminology and GA status, including removal of beta labels, addition of new service documentation pages (RAG and PostgREST), and clarification about systemd cluster support limitations.

Changes

Cohort / File(s) Summary
Documentation - Service Terminology and GA Promotion
docs/development/supported-services.md, docs/services/index.md
Updated terminology from "supported service" to "supporting service"; removed beta designation from services index and added note clarifying current systemd cluster limitations.
Configuration and Release Management
Makefile, changes/unreleased/Changed-20260501-104640.yaml, mkdocs.yml
Updated build comment for terminology consistency; added changelog entry documenting GA promotion; expanded navigation with new service documentation pages (RAG, PostgREST) and development guides (cluster integration tests, supporting service setup).
Documentation Structure
docs/development/running-locally.md
Removed table of contents section from the local development guide.

Poem

🐰 From beta's burrow to the light,
Supporting Services now shine bright!
RAG and PostgREST join the show,
GA status steals the glow ✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Description check ❓ Inconclusive The description is missing a full template structure with Testing, Checklist, and Notes for Reviewers sections, though it provides a clear summary of changes made. Add Testing section (including steps to verify mkdocs builds correctly), complete Checklist items, and Notes for Reviewers to fully align with the repository template.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the main changes: promoting Supporting Services from beta to GA and fixing mkdocs warnings, which aligns with the primary objectives of the PR.
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 docs/PLAT-570/sup-services-beta-update

Review rate limit: 4/5 reviews remaining, refill in 12 minutes.

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

@mmols mmols requested a review from jason-lynch May 1, 2026 16:01
@codacy-production
Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

@@ -1,32 +1,5 @@
# Running the Control Plane locally

- [Running the Control Plane locally](#running-the-control-plane-locally)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Do we have to remove this? I think most people will consume this document in their editor or in GitHub rather than our docs site, and I find the TOC really helpful for navigating it.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I'd also be open to removing all of our development docs from the docs site.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Both Github and VS Code have outline views for viewing the table of contents, so it seemed like a consistent experience across all three places to just remove this. Obviously not every editor will have an outline view / markdown navigation features.

I think having the development docs on the docs site is valuable - it promotes the idea of outside contribution.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Caution

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

⚠️ Outside diff range comments (1)
mkdocs.yml (1)

51-100: ⚠️ Potential issue | 🔴 Critical

Remove or replace the non-existent "redoc-tag" plugin in mkdocs.yml.

The mkdocs build --strict command fails with ERROR - Config value 'plugins': The "redoc-tag" plugin is not installed. There is no PyPI package providing this plugin. The configuration references a plugin that cannot be resolved, preventing the documentation from building at all. Either remove the plugin reference from mkdocs.yml (line 18) if it's no longer needed, or replace it with the correct plugin name/package.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@mkdocs.yml` around lines 51 - 100, The mkdocs build fails because mkdocs.yml
references a non-existent plugin "redoc-tag" under the plugins key; open
mkdocs.yml, locate the plugins section and either remove the "redoc-tag" entry
or replace it with the correct plugin name/package (or a supported redoc plugin)
so mkdocs can resolve plugins during mkdocs build --strict; ensure the plugins
list is valid and run the build to confirm the error is gone.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Outside diff comments:
In `@mkdocs.yml`:
- Around line 51-100: The mkdocs build fails because mkdocs.yml references a
non-existent plugin "redoc-tag" under the plugins key; open mkdocs.yml, locate
the plugins section and either remove the "redoc-tag" entry or replace it with
the correct plugin name/package (or a supported redoc plugin) so mkdocs can
resolve plugins during mkdocs build --strict; ensure the plugins list is valid
and run the build to confirm the error is gone.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: b0142d55-69ce-4c1c-98d7-dd10181f095b

📥 Commits

Reviewing files that changed from the base of the PR and between 1e081a8 and 2d0ba8b.

📒 Files selected for processing (6)
  • Makefile
  • changes/unreleased/Changed-20260501-104640.yaml
  • docs/development/running-locally.md
  • docs/development/supported-services.md
  • docs/services/index.md
  • mkdocs.yml
💤 Files with no reviewable changes (1)
  • docs/development/running-locally.md

@mmols mmols merged commit 0e7da14 into main May 1, 2026
2 of 3 checks passed
@mmols mmols deleted the docs/PLAT-570/sup-services-beta-update branch May 1, 2026 18:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants