docs: add missed changelog entries for v1.0.0

[mmols]

Add missing changelog entries for merged PRs.

 ### Added

 - Added support for zero-downtime node addition using a Spock populate pipeline. Writes can continue
 uninterrupted on existing nodes while a new node syncs via logical replication, replacing the previous
 behavior which required stopping writes during `helm upgrade` (#52)
 - Added a guided walkthrough that progressively builds an active-active PostgreSQL deployment, available
 as documentation, an interactive terminal guide, and a one-click GitHub Codespaces environment (#48)
 - Added the ability to configure the database name, owner, and admin role via Helm values
 (`initdb.database`, `initdb.owner`, `pgEdge.adminUser`). Also added documentation covering all managed
 users, their authentication methods, and how to create additional users or disable passwords (#54)

 ### Changed

 - Rewrote the quickstart documentation for experienced Kubernetes users with a streamlined,
 copy-paste-and-go guide that assumes a working cluster (#46)
 - Updated default Postgres image to 18, CloudNativePG to 1.29, and cert-manager to use the latest release
 (#51)
 - Rewrote the init-spock job from Python to Go with a declarative resource engine that inspects actual
 state and converges toward desired state. Includes parallel execution within dependency phases and reduces the
 Docker image from ~150MB to ~15MB (#50)

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request adds five unreleased changelog entries documenting: zero-downtime node addition via a Spock populate pipeline; a guided active-active PostgreSQL deployment walkthrough; a streamlined Kubernetes quickstart; updated default component versions; and a rewrite of the init-spock job from Python to Go.

Changes

Cohort / File(s)	Summary
Added Features changes/unreleased/Added-20260416-155002.yaml, changes/unreleased/Added-20260416-155011.yaml	Adds zero-downtime node addition using a Spock populate pipeline and introduces a guided walkthrough for building an active-active PostgreSQL deployment (docs, interactive terminal guide, GitHub Codespaces).
Changed Components changes/unreleased/Changed-20260416-155011.yaml, changes/unreleased/Changed-20260416-155041.yaml, changes/unreleased/Changed-20260416-155044.yaml	Rewrites Kubernetes quickstart into a streamlined guide; updates default image/component versions (Postgres, CloudNativePG, cert-manager); rewrites init-spock job from Python to Go with declarative convergence and reduced image size.

Poem

🐰 I hopped through changelogs, nibbling lines of code,
I watched new nodes join without a single mode,
A guided path appears to build clusters bright,
Init-spock learned Go and trimmed its appetite,
Versions bumped, docs polished — I celebrate the load!

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title directly matches the changeset, which adds missing changelog entries for v1.0.0 release.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description check	✅ Passed	The pull request description accurately documents the addition of missing changelog entries, matching the actual file changes in the raw summary.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/PLAT-565/missed-release-notes

---

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

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (2)

changes/unreleased/Added-20260416-155011.yaml (2)

2-2: Remove redundant "Added" prefix in body.

Since kind: Added already indicates this is an addition, starting the body with "Added" is redundant. The PR description itself starts with "A guided walkthrough..." without the prefix.

♻️ Suggested refinement

-body: Added a guided walkthrough that progressively builds an active-active PostgreSQL deployment, available as documentation, an interactive terminal guide, and a one-click GitHub Codespaces environment (`#48`)
+body: A guided walkthrough that progressively builds an active-active PostgreSQL deployment, available as documentation, an interactive terminal guide, and a one-click GitHub Codespaces environment (`#48`)

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@changes/unreleased/Added-20260416-155011.yaml` at line 2, The "body" field
currently begins with a redundant "Added" prefix while the entry is already
labeled with kind: Added; update the YAML by removing the leading "Added " from
the body value so the sentence reads "A guided walkthrough..." instead; target
the body key in the changes/unreleased/Added-20260416-155011.yaml entry and trim
the duplicate prefix, preserving the rest of the description and punctuation.

---

3-3: Consider normalizing timestamp precision.

This timestamp has microsecond precision (.305881) while Changed-20260416-155011.yaml uses millisecond precision (.328). Consistent precision improves uniformity across changelog entries.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@changes/unreleased/Added-20260416-155011.yaml` at line 3, The timestamp value
"2026-04-16T15:50:11.305881-05:00" in Added-20260416-155011.yaml uses
microsecond precision; change it to millisecond precision to match other entries
(e.g., reduce/round the fractional seconds to three digits such as
"2026-04-16T15:50:11.306-05:00"), updating the timestamp string in the file and
ensuring any other changelog entries follow the same millisecond precision
format.

🤖 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/Changed-20260416-155044.yaml`:
- Line 2: Edit the changelog entry's body value: replace the incomplete phrase
"converges toward desired" with "converges toward desired state" so the sentence
reads "...inspects actual state and converges toward desired state." Update the
YAML value for the body key accordingly to ensure the changelog is clear and
grammatical.

---

Nitpick comments:
In `@changes/unreleased/Added-20260416-155011.yaml`:
- Line 2: The "body" field currently begins with a redundant "Added" prefix
while the entry is already labeled with kind: Added; update the YAML by removing
the leading "Added " from the body value so the sentence reads "A guided
walkthrough..." instead; target the body key in the
changes/unreleased/Added-20260416-155011.yaml entry and trim the duplicate
prefix, preserving the rest of the description and punctuation.
- Line 3: The timestamp value "2026-04-16T15:50:11.305881-05:00" in
Added-20260416-155011.yaml uses microsecond precision; change it to millisecond
precision to match other entries (e.g., reduce/round the fractional seconds to
three digits such as "2026-04-16T15:50:11.306-05:00"), updating the timestamp
string in the file and ensuring any other changelog entries follow the same
millisecond precision format.

🪄 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: 3af0428b-392e-4260-b974-29cc88c5c9ac

📥 Commits

Reviewing files that changed from the base of the PR and between 7a11168 and 0b16e62.

📒 Files selected for processing (5)

• changes/unreleased/Added-20260416-155002.yaml
• changes/unreleased/Added-20260416-155011.yaml
• changes/unreleased/Changed-20260416-155011.yaml
• changes/unreleased/Changed-20260416-155041.yaml
• changes/unreleased/Changed-20260416-155044.yaml

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{TIP This summary will be updated as you push new changes. Give us feedback}