Update changelog for 5.2.0

[justin808]

Summary

• stamp the changelog for version 5.2.0
• carry forward the existing Unreleased entries
• add missing user-visible entries from PRs 348, 364, 371, and 363
• update the Unreleased and 5.2.0 comparison links

Classification sweep

Reviewed all 18 merged PRs in v5.1.1..origin/main; all commits mapped to PRs and no unknown rows remained. Contributor-only, CI-only, internal workflow, and docs-only PRs without existing changelog entries were intentionally omitted.

Validation

• git diff --check
• bundle exec rspec spec/rakelib/create_release_spec.rb (3 examples, 0 failures)
• release policy verification confirms 5.2.0 is a valid minor bump from 5.1.1
• codex review --uncommitted -c 'model="gpt-5.4"' closeout loop completed; one accepted finding fixed, one base-branch-link suggestion rejected because the changelog skill requires the configured main branch

After merge, run bundle exec rake release from clean main to publish 5.2.0 and create the GitHub release from this section.

[coderabbitai]

Warning

Review limit reached

@justin808, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 2 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 8b5788ce-bc67-4183-b309-b92c2a58b69a

📥 Commits

Reviewing files that changed from the base of the PR and between 58b7329 and 550ca84.

📒 Files selected for processing (1)

• CHANGELOG.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch jg-codex/changelog-5.2.0

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[greptile-apps]

Greptile Summary

This PR stamps the changelog for the 5.2.0 release. The main changes are:

• Adds the 5.2.0 release section.
• Moves current release notes out of Unreleased.
• Adds missing user-visible entries for recent PRs.
• Updates the Unreleased and 5.2.0 comparison links.

Confidence Score: 5/5

This looks safe to merge.

• No blocking issues found in the changed code.

Important Files Changed

Filename	Overview
CHANGELOG.md	Adds the 5.2.0 changelog section and updates release comparison links.

_{Reviews (1): Last reviewed commit: "Update changelog for 5.2.0" | Re-trigger Greptile}

[claude]

Nit: the stamped release date is 2026-07-10, but today is 2026-07-11 and the PR body says the actual bundle exec rake release run happens after this merges. If the release doesn't actually publish on the 10th, this date will be stale on arrival. Worth double-checking against the real publish date before/at merge time (or bumping it right before running rake release).

[claude]

Review: Update changelog for 5.2.0

Overview

This PR is a pure CHANGELOG.md edit that stamps the [Unreleased] entries under a new [5.2.0] - 2026-07-10 header, adds four "missing" user-visible entries from PRs #348, #364, #371, and #363, and repoints the [Unreleased] / [5.2.0] compare links. No source code changes.

Verification performed

• Confirmed all four newly-added entries ([codex] Document shared staging Postgres pattern #348, Document scale-to-zero cost posture for demos #364, [codex] Add AI rollout quick start callout #371, Validate selected setup templates and review-app health #363) are merged PRs, and diffed each against main to check the changelog wording matches the actual shipped behavior:
  • [codex] Document shared staging Postgres pattern #348 — diff removes pre_deletion: rails/rake db:drop from controlplane.yml examples and documents the shared-Postgres teardown hazard. Matches the "Changed" entry accurately (despite the PR title being about a different aspect of the same change).
  • [codex] Add AI rollout quick start callout #371 — diff updates ai_github_flow_prompt.rb and its spec to have the rollout prompt install a missing cpflow gem or report the blocker. Matches the entry.
  • Document scale-to-zero cost posture for demos #364 — diff swaps the serverless/scale-to-zero guidance for capacityAI: true guidance in docs/tips.md / docs/ci-automation.md. Matches the entry.
  • Validate selected setup templates and review-app health #363 — diff shows both the doctor/setup-app template-validation fix (lib/core/doctor_service.rb, template_parser.rb) and the review-app health-check wait step (cpflow-deploy-review-app.yml), so listing it under two separate ### Fixed bullets is justified — both are distinct, user-visible fixes from the same PR.
• Category placement (Added / Changed / Fixed) is consistent with how this changelog has classified similar entries historically (e.g., removals are filed under Changed, not a separate Removed heading, matching existing convention).
• The [Unreleased] link was changed from ...compare/v5.1.1...HEAD to ...compare/v5.2.0...main. Per the PR description this was a deliberate choice tied to this repo's configured base branch (main, per AGENTS.md), and a codex review suggestion to change it was already considered and rejected for a documented reason. No issue.
• Diff structure is sound: all carried-forward entries move cleanly under the new ## [5.2.0] header, ## [Unreleased] is left empty (correct keepachangelog practice pending new work), and no headings or links were left dangling.

Minor nit (posted inline)

• The stamped date 2026-07-10 is one day before today (2026-07-11), and the PR description says actual publishing (bundle exec rake release) happens after merge. If the real release lands later, this header date will already be stale. Worth confirming/adjusting the date at merge/release time.

Risk

Very low — no runtime code paths are touched, only documentation/changelog content. The main risk category (accuracy of claims) was spot-checked above and found correct.