Skip to content

docs: cleanup changelog for 0.7.0#317

Merged
mmols merged 4 commits intomainfrom
docs/release-0.7.0-changes
Mar 25, 2026
Merged

docs: cleanup changelog for 0.7.0#317
mmols merged 4 commits intomainfrom
docs/release-0.7.0-changes

Conversation

@mmols
Copy link
Copy Markdown
Member

@mmols mmols commented Mar 24, 2026

This PR cleans up unreleased changes to properly reflect user-facing items since our last release. It manipulates a timestamp or two to push Supporting services to the top, and merges together some past changie entries into higher level items.

v0.7.0 - 2026-03-25

Added

  • Supporting services (beta) — Deploy supporting services alongside databases. This release includes the pgEdge Postgres MCP Server, with automatic database credential provisioning, high-availability connection routing, and declarative configuration.
  • Added patroni_port to the database and instance APIs.
  • Added ability to configure per-component log levels.
  • Added a default value for the host_id configuration setting. It will now default to the short hostname (hostname -s) of the host machine.
  • Added guided walkthrough with GitHub Codespaces support.
  • Added support for Postgres 16.13, 17.9, and 18.3. Default version is now 18.3.
  • Added stop/start instance operations to the client library.
  • Etcd mode reconfiguration — Hosts can now switch between etcd server and client modes at runtime, with support for host identity changes via peer URL updates.
  • Scoped tasks and new task endpoints — Tasks are now scoped to databases and hosts, with new list/get endpoints for better observability. The remove-host API now returns a task for tracking removal progress.
  • Stable random port assignments — Randomly assigned ports now persist across instance restarts and database updates.

Changed

  • Improved disaster recovery — Better quorum loss handling, host removal resilience, and crash recovery.
  • Breaking: Replaced hostname and ipv4_address fields in the API with peer_addresses and client_addresses for host endpoints and addresses for instance and service instance endpoints.

Fixed

  • Fixed a bug that prevented database deletion when we failed to create the Swarm service.
  • Replaced fixed 100-second sync wait when adding a node with configurable health-based polling.
  • Fixed sync event refresh blocking updates when Spock node is not configured.
  • Fixed panics during task and workflow cancellation.
  • Fixed add-node failing silently when Spock sync event is not confirmed.
  • Fixed incomplete server shutdown that could leave the workflow engine running without required services.
  • Fixed stale resource state blocking updates.
  • Fixed IPAM subnet exhaustion after repeated database create/delete cycles by releasing subnets on network deletion.

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Mar 24, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: ba5286e4-3b6e-42f9-bce9-5452ff2b9b99

📥 Commits

Reviewing files that changed from the base of the PR and between 33d4bf1 and 288a339.

📒 Files selected for processing (1)
  • changes/unreleased/Added-20260324-100004.yaml
🚧 Files skipped from review as they are similar to previous changes (1)
  • changes/unreleased/Added-20260324-100004.yaml

📝 Walkthrough

Walkthrough

Removed multiple dated unreleased changelog entries, updated text in a few existing entries, and added a set of new Added/Changed/Fixed YAML entries under changes/unreleased. No code, runtime logic, or public API/entity declarations were modified.

Changes

Cohort / File(s) Summary
Removed Added entries
changes/unreleased/Added-20260109-223536.yaml, changes/unreleased/Added-20260114-162946.yaml, changes/unreleased/Added-20260114-173755.yaml, changes/unreleased/Added-20260115-010344.yaml, changes/unreleased/Added-20260122-185129.yaml, changes/unreleased/Added-20260209-091508.yaml, changes/unreleased/Added-20260209-091526.yaml, changes/unreleased/Added-20260216-213934.yaml
Deleted eight prior "Added" release-note files (etcd client/server reconfiguration, host-scoped tasks, non-database tasks, Host API fields, peer URL updates, client service JSON tags, database listing response, quorum recovery notes).
Removed Changed entries
changes/unreleased/Changed-20260114-163406.yaml, changes/unreleased/Changed-20260209-091536.yaml, changes/unreleased/Changed-20260306-155827.yaml, changes/unreleased/Changed-20260306-160015.yaml
Deleted four prior "Changed" release-note files describing API/response changes and address field/schema replacements for host/instance endpoints.
Text refinements
changes/unreleased/Added-20260225-091421.yaml, changes/unreleased/Fixed-20260218-230320.yaml, changes/unreleased/Fixed-20260220-191533.yaml
Updated changelog text: removed a host-specific qualifier and clarified/simplified two fix descriptions (minor wording edits only).
New Added entries
changes/unreleased/Added-20260324-100001.yaml, changes/unreleased/Added-20260324-100002.yaml, changes/unreleased/Added-20260324-100004.yaml, changes/unreleased/Added-20260324-100005.yaml, changes/unreleased/Added-20260324-100006.yaml, changes/unreleased/Added-20260324-100007.yaml, changes/unreleased/Added-20260324-100009.yaml
Added seven new "Added" release-note files covering supporting services deployment (pgEdge MCP), a guided Codespaces walkthrough, Postgres version additions and default change, client stop/start operations, etcd mode reconfiguration and peer updates, scoped tasks and task endpoints, and stable random port assignments.
New Changed entries
changes/unreleased/Changed-20260324-100003.yaml, changes/unreleased/Changed-20260324-100004.yaml
Added two "Changed" entries: improved disaster recovery handling and a breaking API schema change replacing hostname/ipv4_address with peer_addresses/client_addresses/addresses.
New Fixed entries
changes/unreleased/Fixed-20260324-100001.yaml, changes/unreleased/Fixed-20260324-100002.yaml, changes/unreleased/Fixed-20260324-100003.yaml, changes/unreleased/Fixed-20260324-100004.yaml, changes/unreleased/Fixed-20260324-100006.yaml
Added five "Fixed" entries addressing task/workflow cancellation panics, add-node sync confirmation, incomplete server shutdown, stale resource state blocking updates, and IPAM subnet exhaustion on repeated create/delete cycles.

Poem

🐇 I nibble on bytes and tidy the log,
Old notes hop away through a neat little fog.
New entries sprout—ports, Postgres, and care,
Etcd and tasks settle warm in their lair.
Hooray for a changelog all fresh and aware!

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title 'docs: cleanup changelog for 0.7.0' accurately and concisely describes the main change: reorganizing and cleaning up unreleased changelog entries for the v0.7.0 release.
Description check ✅ Passed The PR description provides a clear summary and comprehensive changelog for v0.7.0 with Added, Changed, and Fixed sections. However, the Testing and Checklist sections from the template are missing.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ 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/release-0.7.0-changes

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

Copy link
Copy Markdown
Contributor

@tsivaprasad tsivaprasad left a comment

Choose a reason for hiding this comment

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

The following unreleased files have not been updated:
Added-20260225-091421.yaml
Added-20260303-092813.yaml
Added-20260306-160121.yaml

Is there any reason for this, and are these files in good?

@mmols
Copy link
Copy Markdown
Member Author

mmols commented Mar 25, 2026

@tsivaprasad

The following unreleased files have not been updated:
Added-20260225-091421.yaml
Added-20260303-092813.yaml
Added-20260306-160121.yaml

Is there any reason for this, and are these files in good?

These all looked good as-is, so i kept them as-is.

Copy link
Copy Markdown
Contributor

@rshoemaker rshoemaker left a comment

Choose a reason for hiding this comment

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

Looks good.

@mmols mmols merged commit 1d7f20b into main Mar 25, 2026
3 checks passed
@mmols mmols deleted the docs/release-0.7.0-changes branch March 25, 2026 16:58
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.

4 participants