chore: add missing changelog entries#370
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
📝 WalkthroughWalkthroughThis PR adds and updates multiple changelog entries documenting recent product features, bug fixes, and breaking changes. The entries cover service credential management, PostgREST and systemd support, port conflict detection, identifier validation, and various infrastructure improvements, along with one cleanup of a superseded entry. ChangesChangelog Entries
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Review rate limit: 0/1 reviews remaining, refill in 60 minutes.Comment |
Up to standards ✅🟢 Issues
|
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@changes/unreleased/Added-20260331-120000.yaml`:
- Line 2: The changelog entry states the server binary was renamed but the CLI
root command still uses Use: "control-plane" while .goreleaser.yaml sets the
artifact name to pgedge-control-plane; decide which was intended and make
matching changes: if only the produced artifact filename changed, update the
changelog (Added-20260331-120000.yaml) to say "renamed artifact file to
pgedge-control-plane (CLI command remains control-plane)"; if the CLI command
was also meant to change, update server/cmd/root.go to Use:
"pgedge-control-plane" (and any docs/tests referencing "control-plane") so code,
.goreleaser.yaml, and the changelog are consistent.
🪄 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: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 6af22d05-5410-42a2-ae5f-18e08cd979c1
📒 Files selected for processing (19)
changes/unreleased/Added-20260331-120000.yamlchanges/unreleased/Added-20260403-120000.yamlchanges/unreleased/Added-20260403-130000.yamlchanges/unreleased/Added-20260406-120000.yamlchanges/unreleased/Added-20260414-120000.yamlchanges/unreleased/Added-20260417-120000.yamlchanges/unreleased/Added-20260417-130000.yamlchanges/unreleased/Changed-20260421-130000.yamlchanges/unreleased/Changed-20260422-130000.yamlchanges/unreleased/Changed-20260424-130000.yamlchanges/unreleased/Fixed-20260409-120000.yamlchanges/unreleased/Fixed-20260409-130000.yamlchanges/unreleased/Fixed-20260416-120000.yamlchanges/unreleased/Fixed-20260420-120000.yamlchanges/unreleased/Fixed-20260421-120000.yamlchanges/unreleased/Fixed-20260422-120000.yamlchanges/unreleased/Fixed-20260424-120000.yamlchanges/unreleased/Fixed-20260427-120000.yamlchanges/unreleased/Fixed-20260428-120000.yaml
| @@ -0,0 +1,3 @@ | |||
| kind: Added | |||
| body: Renamed the server binary from `control-plane` to `pgedge-control-plane` to reduce conflicts with other system packages. | |||
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Read-only verification of old/new naming across user-facing and release metadata.
rg -n -C2 --iglob 'Makefile' --iglob '.goreleaser.yaml' --iglob '*.go' \
'\bcontrol-plane\b|pgedge-control-plane' .Repository: pgEdge/control-plane
Length of output: 50378
🏁 Script executed:
# Check what files are modified in the current changeset
git diff HEAD~1 --name-only 2>/dev/null | head -20 || git status --short 2>/dev/null | head -20 || echo "Unable to get file changes"Repository: pgEdge/control-plane
Length of output: 46
🏁 Script executed:
# Focused check: was server/cmd/root.go modified?
if git log --oneline -1 2>/dev/null | grep -q .; then
echo "=== Files modified in last commit ==="
git diff HEAD~1 --name-only 2>/dev/null
else
echo "Git history check failed; searching for server/cmd/root.go with Use field:"
grep -n "Use:.*control-plane" ./server/cmd/root.go 2>/dev/null || echo "Not found or file absent"
fiRepository: pgEdge/control-plane
Length of output: 104
🏁 Script executed:
# Verify the exact binary output name in build configs
echo "=== Checking Makefile for binary name ==="
grep -n "pgedge-control-plane\|control-plane" ./Makefile 2>/dev/null | grep -E "(name:|CONTROL_PLANE|^[0-9]+:\s*(name|output|binary))" || echo "Pattern not found"
echo -e "\n=== Checking .goreleaser.yaml for binary/image references ==="
grep -n "pgedge-control-plane\|control-plane" ./.goreleaser.yaml 2>/dev/null | head -10 || echo "File not found or no matches"Repository: pgEdge/control-plane
Length of output: 777
🏁 Script executed:
# Check the actual server/cmd/root.go to see if Use field is still "control-plane"
grep -A2 -B2 "Use:" ./server/cmd/root.go | head -20Repository: pgEdge/control-plane
Length of output: 272
Verify changelog scope: binary artifact vs. CLI command rename.
The changelog says "Renamed the server binary," but the CLI command name in server/cmd/root.go still shows Use: "control-plane" while .goreleaser.yaml shows the binary artifact is pgedge-control-plane. If only the artifact filename was renamed (not the command users invoke), clarify this in the changelog to avoid misleading release consumers.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@changes/unreleased/Added-20260331-120000.yaml` at line 2, The changelog entry
states the server binary was renamed but the CLI root command still uses Use:
"control-plane" while .goreleaser.yaml sets the artifact name to
pgedge-control-plane; decide which was intended and make matching changes: if
only the produced artifact filename changed, update the changelog
(Added-20260331-120000.yaml) to say "renamed artifact file to
pgedge-control-plane (CLI command remains control-plane)"; if the CLI command
was also meant to change, update server/cmd/root.go to Use:
"pgedge-control-plane" (and any docs/tests referencing "control-plane") so code,
.goreleaser.yaml, and the changelog are consistent.
There was a problem hiding this comment.
Seems like the humans are having a chat. I'll hop back into my burrow for now. If you need me again, just tag @coderabbitai in a new comment, and I'll come hopping out!
jason-lynch
left a comment
There was a problem hiding this comment.
Thanks for doing this! I left a few comments around the systemd portions because that's what I'm familiar with. We don't need granular release notes for systemd-related features and fixes because it didn't exist in the last release.
Could you please also double check that the service-related entries only include changes to things that were present in v0.7.0?
jason-lynch
left a comment
There was a problem hiding this comment.
Awesome! Thank you for doing this.
Fixup missing changelog entries for the next release:
✗ changie batch minor --dry-run
v0.8.0 - 2026-04-29
Added
control-planetopgedge-control-planeto reduce conflicts with other system packages.cpu_quotaandmemory_maxin the instance specification, enforced through systemd cgroup integration.connect_asfield for service credentials — Services can now explicitly specify which database user they authenticate as by referencing adatabase_usersentry, replacing auto-generated service accounts with direct, auditable credential assignment.database_usersconfiguration are now automatically transferred to new nodes when they join a database.Changed
connect_asfield is now required when creating or updating services of any type (MCP, PostgREST, RAG) — requests that omit this field will be rejected with a validation error.db_anon_roleto be explicitly set in the service configuration — the previously implicitpgedge_application_read_onlydefault has been removed.pgedge_applicationandpgedge_application_read_onlybuilt-in database roles — These roles are no longer created for new databases. The names are no longer reserved and may be used freely for custom database users.Fixed
extra_networksspecified inorchestrator_optsnot being attached to service containers (MCP, PostgREST, RAG).pg_hba.confis correct when replicas begin syncing.PLAT-570