Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 0 additions & 3 deletions changes/unreleased/Added-20260309-165318.yaml

This file was deleted.

3 changes: 3 additions & 0 deletions changes/unreleased/Added-20260331-120000.yaml
Original file line number Diff line number Diff line change
@@ -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.
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot Apr 29, 2026

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

🧩 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"
fi

Repository: 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 -20

Repository: 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.

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.

@tsivaprasad I've opened a PR to fix this: #371

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

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!

time: 2026-03-31T12:00:00.000000-04:00
3 changes: 3 additions & 0 deletions changes/unreleased/Added-20260403-120000.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
kind: Added
body: Added PostgREST as a supported service type — Deploy the PostgREST REST API server alongside your database with automatic credential provisioning, upfront schema and role validation, and configurable connection pool settings.
time: 2026-04-03T12:00:00.000000-04:00
3 changes: 3 additions & 0 deletions changes/unreleased/Added-20260403-130000.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
kind: Added
body: Added preliminary support for systemd as an alternative to Docker Swarm. This feature is currently in "preview" status. You can read more about it in the [systemd page](https://docs.pgedge.com/control-plane/v0-8/installation/systemd) of our docs.
time: 2026-04-03T13:00:00.000000-04:00
3 changes: 3 additions & 0 deletions changes/unreleased/Added-20260414-120000.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
kind: Added
body: Added `connect_as` field for service credentials — Services can now explicitly specify which database user they authenticate as by referencing a `database_users` entry, replacing auto-generated service accounts with direct, auditable credential assignment.
time: 2026-04-14T12:00:00.000000-04:00
3 changes: 3 additions & 0 deletions changes/unreleased/Added-20260417-120000.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
kind: Added
body: Added automatic role transfer when expanding a database cluster — PostgreSQL roles created outside the standard `database_users` configuration are now automatically transferred to new nodes when they join a database.
time: 2026-04-17T12:00:00.000000-04:00
3 changes: 3 additions & 0 deletions changes/unreleased/Added-20260417-130000.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
kind: Added
body: Extended stable random port assignments to service instances — Ports assigned to MCP, PostgREST, and RAG services are now persisted and reused across restarts and database updates, consistent with the behaviour already in place for database instances.
time: 2026-04-17T13:00:00.000000-04:00
2 changes: 1 addition & 1 deletion changes/unreleased/Added-20260422-004204.yaml
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
kind: Added
body: Add RAG service with hybrid vector + LLM search
body: Added RAG as a supported service type — Deploy a retrieval-augmented generation server alongside your database with hybrid vector and keyword search, automatic credential provisioning, and support for OpenAI, Voyage AI, Anthropic, and Ollama providers.
time: 2026-04-22T00:42:04.283582+05:30
3 changes: 3 additions & 0 deletions changes/unreleased/Changed-20260421-130000.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
kind: Changed
body: "**Breaking:** The `connect_as` field 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."
time: 2026-04-21T13:00:00.000000-04:00
3 changes: 3 additions & 0 deletions changes/unreleased/Changed-20260424-130000.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
kind: Changed
body: Removed the `pgedge_application` and `pgedge_application_read_only` built-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.
time: 2026-04-24T13:00:00.000000-04:00
3 changes: 3 additions & 0 deletions changes/unreleased/Fixed-20260409-120000.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
kind: Fixed
body: Fixed port conflicts between services on the same host producing opaque deployment errors — Port conflicts are now detected at creation time and rejected with a clear validation message.
time: 2026-04-09T12:00:00.000000-04:00
3 changes: 3 additions & 0 deletions changes/unreleased/Fixed-20260409-130000.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
kind: Fixed
body: Fixed `extra_networks` specified in `orchestrator_opts` not being attached to service containers (MCP, PostgREST, RAG).
time: 2026-04-09T13:00:00.000000-04:00
3 changes: 3 additions & 0 deletions changes/unreleased/Fixed-20260421-120000.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
kind: Fixed
body: Fixed upgrade path from v0.6.2 — Databases created before v0.7.0 that were missing replication slot resources are now automatically repaired during state migration.
time: 2026-04-21T12:00:00.000000-04:00
3 changes: 3 additions & 0 deletions changes/unreleased/Fixed-20260424-120000.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
kind: Changed
body: "**Breaking:** Database, host, cluster, and service identifiers are now validated to comply with RFC 1035 name requirements — IDs must be 1–36 characters, contain only lowercase letters, digits, and hyphens, and start and end with a letter or digit. The combined length of a database ID and service ID may not exceed 53 characters."
time: 2026-04-24T12:00:00.000000-04:00
3 changes: 3 additions & 0 deletions changes/unreleased/Fixed-20260427-120000.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
kind: Fixed
body: Fixed embedded etcd clients connecting to all cluster members instead of only their own endpoint — This could cause connectivity issues when cluster membership changed.
time: 2026-04-27T12:00:00.000000-04:00