Preparing release notes for PEP/PG version updates

[susan-pgedge]

Summary by CodeRabbit

• Documentation
  • Updated release notes with Postgres versions 16.14, 17.10, and 18.4, along with corresponding enterprise package versions.
  • Added component updates for libpq 18.4 and Common 290.

[coderabbitai]

Walkthrough

This PR updates the 5/14/2026 release notes entry in the Enterprise Postgres documentation by replacing aggregate version descriptions with explicit per-package version listings for pgedge-enterprise-postgres and pgedge-enterprise-all, and adds new component update bullets for libpq 18.4 and Common 290 (debs only).

Changes

Release Notes Documentation

Layer / File(s)	Summary
5/14/2026 release notes entry docs/enterprise/pep_rel_notes.md	Release notes section updated with explicit per-package version listings for Postgres versions 16.14, 17.10, 18.4 across pgedge-enterprise-postgres and pgedge-enterprise-all, plus new component update entries for libpq 18.4 and Common 290 (debs only).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• pgEdge/pgedge-docs#64: Both PRs update docs/enterprise/pep_rel_notes.md release-note entries for specific dates and components.
• pgEdge/pgedge-docs#59: Both PRs modify release-note entries in docs/enterprise/pep_rel_notes.md with updated pgEdge Enterprise Postgres versions and component bullets.

Suggested reviewers

• dpage

🚥 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: updating release notes documentation with new Postgres and package versions.
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 pep_package_update

---

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

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

[cloudflare-workers-and-pages]

Deploying pgedge-docs with    Cloudflare Pages

Latest commit:	a90834d
Status:	🚫  Build failed.

View logs

[coderabbitai]

🧹 Nitpick comments (1)

docs/enterprise/pep_rel_notes.md (1)

5-18: ⚡ Quick win

Consider aligning with the established release notes format for consistency.

The new format lists each Postgres version separately with nested package bullets, which differs from the established pattern used in previous entries (e.g., lines 53-54, 82-83). The historical format groups all versions compactly:

* pgEdge Enterprise Postgres versions 16.14, 17.10, and 18.4
* pgEdge Meta Packages (pgedge-enterprise-postgres and pgedge-enterprise-all, versions 16.14, 17.10, 18.4)

This approach is more concise, maintains document consistency, and avoids redundancy where the nested bullets simply repeat the version already stated in the parent.

📋 Suggested reformatting to match historical pattern

-* Postgres version update: pgEdge Enterprise Postgres 16.14
-
-    * pgedge-enterprise-postgres 16.14
-    * pgedge-enterprise-all 16.14
-
-* Postgres version update: pgEdge Enterprise Postgres 17.10
-
-    * pgedge-enterprise-postgres 17.10
-    * pgedge-enterprise-all 17.10
-
-* Postgres version update: pgEdge Enterprise Postgres 18.4
-
-    * pgedge-enterprise-postgres 18.4
-    * pgedge-enterprise-all 18.4
+* pgEdge Enterprise Postgres versions 16.14, 17.10, and 18.4
+* pgEdge Meta Packages (pgedge-enterprise-postgres and pgedge-enterprise-all, versions 16.14, 17.10, 18.4)

🤖 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 `@docs/enterprise/pep_rel_notes.md` around lines 5 - 18, Consolidate the three
separate Postgres entries into the established compact release-note format:
replace the three blocks that list "pgEdge Enterprise Postgres 16.14", "17.10",
and "18.4" (and their nested "pgedge-enterprise-postgres" and
"pgedge-enterprise-all" bullets) with two concise bullets that mirror historical
entries—one bullet like "pgEdge Enterprise Postgres versions 16.14, 17.10, and
18.4" and a second like "pgEdge Meta Packages (pgedge-enterprise-postgres and
pgedge-enterprise-all, versions 16.14, 17.10, 18.4)"; update the content near
the existing postgres blocks so the package names and versions remain present
but not redundantly repeated in nested lists.

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

Nitpick comments:
In `@docs/enterprise/pep_rel_notes.md`:
- Around line 5-18: Consolidate the three separate Postgres entries into the
established compact release-note format: replace the three blocks that list
"pgEdge Enterprise Postgres 16.14", "17.10", and "18.4" (and their nested
"pgedge-enterprise-postgres" and "pgedge-enterprise-all" bullets) with two
concise bullets that mirror historical entries—one bullet like "pgEdge
Enterprise Postgres versions 16.14, 17.10, and 18.4" and a second like "pgEdge
Meta Packages (pgedge-enterprise-postgres and pgedge-enterprise-all, versions
16.14, 17.10, 18.4)"; update the content near the existing postgres blocks so
the package names and versions remain present but not redundantly repeated in
nested lists.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 8a029cfa-4890-40f8-b2e7-917c09fe095e

📥 Commits

Reviewing files that changed from the base of the PR and between 850cef9 and a90834d.

📒 Files selected for processing (1)

• docs/enterprise/pep_rel_notes.md