chore: added missing changelog entries#441
Conversation
|
Warning Review limit reached
Next review available in: 47 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughChangesRelease note entries
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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. 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 current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@changes/unreleased/Fixed-20260716-000000.yaml`:
- Line 2: Update the changelog entry’s body value to quote the entire string,
preserving the existing message while ensuring the embedded “version”: “latest”
text and its colon-space sequence are valid YAML.
🪄 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 Plus
Run ID: 02e8ffcb-f3a4-49d9-8e8a-fbb1ef039792
📒 Files selected for processing (12)
changes/unreleased/Added-20260625-000000.yamlchanges/unreleased/Added-20260701-000000.yamlchanges/unreleased/Added-20260701-000001.yamlchanges/unreleased/Added-20260707-000000.yamlchanges/unreleased/Added-20260707-000001.yamlchanges/unreleased/Added-20260713-000000.yamlchanges/unreleased/Added-20260723-000000.yamlchanges/unreleased/Fixed-20260706-000000.yamlchanges/unreleased/Fixed-20260708-000000.yamlchanges/unreleased/Fixed-20260715-000001.yamlchanges/unreleased/Fixed-20260716-000000.yamlchanges/unreleased/Security-20260721-000000.yaml
Fixup missing changelog entries for the next release:
✗ changie batch minor --dry-run
v0.10.0 - 2026-07-23
Added
spockfrompostgresql_conf.shared_preload_libraries, preventing accidentaldisabling of the replication extension.
GET /v1/databases/{id}?include=available_upgradesto list newerstable images within the same Postgres major and Spock major version
bucket, and
POST /v1/databases/{id}/upgradeto apply an upgradewithout changing the Postgres major version.
via
orchestrator_opts.swarm.image. pgEdge-formatted image tags arevalidated against the spec's declared versions; unrecognized tags are
accepted without version checks. The Control Plane also persists the
resolved image at creation time, preventing silent image changes
during Control Plane upgrades.
update with manifest refreshes without requiring a Control Plane
upgrade.
when no IPv4 address is found during IP autodetection.
interrupting long-running operations rather than waiting for them to
complete.
repositories on every release, enabling installation via
dnfandapt-getin addition to the existing Docker and binary distributionmethods.
Changed
password_encryptionfrommd5toscram-sha-256. If you're using the default password encryption,every role in a database's
database_userswill be automaticallyupdated to
scram-sha-256the next time you update that database.Roles created outside of
database_userswill need their passwordsupdated manually. To keep using
md5, setpostgresql_conf.password_encryptiontomd5in your database spec.Fixed
planned for creation in the right reconciliation phase, causing
reconciliation errors.
IPv4-mapped IPv6 addresses (e.g.
::ffff:192.168.1.1) on dual-stackhosts.
instances due to replication slot timing during instance
initialization.
"version": "latest"failed at runtime because
"latest"was not registered in theversion map.
Security
golang.org/x/crypto v0.54.0, golang.org/x/net v0.57.0) and bumped
the Go toolchain to 1.26.5 to remediate Trivy-flagged CVEs.
database creation and updates.
PLAT-696