auto: sync mkdocs.yml nav from SSOT

[maqeel75]

mkdocs.yml Drift Report — pgedge-docs

Missing from mkdocs.yml nav (in SSOT, absent here)

• MISSING spock-5011 (Spock 5.0.11) — label v5.0.11 → https://github.com/pgEdge/spock.git?branch=v5.0.11
• MISSING ace-211 (pgEdge ACE 2.1.1) — label v2.1.1 → https://github.com/pgEdge/ace.git?branch=v2.1.1
• MISSING pgedge-snowflake-26 (pgEdge Snowflake 2.6.0) — label v2.6 → https://github.com/pgEdge/snowflake.git?branch=v2.6.0
• MISSING pgvector-085 (pgvector 0.8.5) — label v0.8.5 → https://github.com/pgEdge/3rd-party-docs.git?branch=pgvector085

New products — no nav block exists (manual placement required)

• NEW PRODUCT pg19-beta2 (PostgreSQL) — https://github.com/pgEdge/3rd-party-docs.git?branch=pg19beta2

---

0 ref update(s), 4 missing, 0 stale, 1 new product(s), 0 new section(s)

---

Generated by sync-mkdocs

Summary by CodeRabbit

• Documentation
  • Added versioned documentation entries for ACE v2.1.1, Snowflake v2.6, Spock v5.0.11, and pgvector community extensions v0.8.5.
  • Updated documentation navigation to make these releases available to readers.

[coderabbitai]

Walkthrough

Updated mkdocs.yml to add versioned documentation navigation entries for ACE, Snowflake, Spock v5, and pgvector community extensions.

Changes

Documentation navigation

Layer / File(s)	Summary
Release navigation imports mkdocs.yml	Adds ACE v2.1.1, Snowflake v2.6, Spock v5 v5.0.11, and pgvector v0.8.5 versioned documentation entries.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• pgEdge/pgedge-docs#117: Updates the same versioned documentation navigation in mkdocs.yml.
• pgEdge/pgedge-docs#132: Modifies the ACE version import list in mkdocs.yml.
• pgEdge/pgedge-docs#134: Adds similar versioned navigation imports in mkdocs.yml.

🚥 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 clearly describes the automated sync of mkdocs.yml navigation from the SSOT, matching the main change.
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.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch auto/sync-mkdocs

---

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

[codacy-production]

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

[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 `@mkdocs.yml`:
- Line 594: Add the missing PostgreSQL Beta 2 navigation entry to mkdocs.yml,
manually placing the pg19-beta2 product imported from the pg19beta2 branch
alongside the existing version imports. Preserve the current navigation
structure and ordering while completing the SSOT sync.

🪄 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 129ae0df-b9c1-4712-a32b-7e970c757aa7

📥 Commits

Reviewing files that changed from the base of the PR and between 9de1632 and cd0da4b.

📒 Files selected for processing (1)

• mkdocs.yml

[coderabbitai]

🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win

Add the PostgreSQL Beta 2 navigation entry before merging.

The four version imports are present, but the PR objective also requires manual placement of the new pg19-beta2 product from the pg19beta2 branch. This navigation entry is still absent from mkdocs.yml, so the SSOT sync remains incomplete.

🤖 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 `@mkdocs.yml` at line 594, Add the missing PostgreSQL Beta 2 navigation entry
to mkdocs.yml, manually placing the pg19-beta2 product imported from the
pg19beta2 branch alongside the existing version imports. Preserve the current
navigation structure and ordering while completing the SSOT sync.