build(release): bump version to v0.9.0#409
Open
jason-lynch wants to merge 11 commits into
Open
Conversation
Up to standards ✅🟢 Issues
|
| Category | Results |
|---|---|
| Complexity | 1 medium |
🟢 Metrics 0 complexity · 5 duplication
Metric Results Complexity 0 Duplication 5
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
|
Warning Review limit reached
More reviews will be available in 37 minutes and 3 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?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 credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. 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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughBumps the API version from Changesv0.9.0 Release Artifacts
Service Orchestration and Monitoring Enhancements
Resource Migration for Scheduled Jobs
Poem
🚥 Pre-merge checks | ✅ 3 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
docs/installation/systemd.md (1)
128-158:⚠️ Potential issue | 🟠 Major | ⚡ Quick winVersion mismatch between RPM and Deb installation sections.
The RPM package section (line 133) specifies
VERSION="v0.9.0", but the Deb package section (line 151) still specifiesVERSION="v0.8.0". For a consistent v0.9.0 release, both installation paths must target the same version.🔧 Proposed fix for the Deb section
# Set the version to install -VERSION="v0.8.0" +VERSION="v0.9.0"🤖 Prompt for 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. In `@docs/installation/systemd.md` around lines 128 - 158, The Deb Package installation section has an outdated version variable that does not match the RPM section. In the Deb Package section, change the VERSION variable from v0.8.0 to v0.9.0 to ensure both RPM and Deb installation paths are consistent and target the same release version. This single-line change in the VERSION assignment will automatically apply the correct version to all subsequent curl and install commands in that section.
🤖 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.
Outside diff comments:
In `@docs/installation/systemd.md`:
- Around line 128-158: The Deb Package installation section has an outdated
version variable that does not match the RPM section. In the Deb Package
section, change the VERSION variable from v0.8.0 to v0.9.0 to ensure both RPM
and Deb installation paths are consistent and target the same release version.
This single-line change in the VERSION assignment will automatically apply the
correct version to all subsequent curl and install commands in that section.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 7ebcf69f-f497-412f-95e1-7ddfd5152727
⛔ Files ignored due to path filters (5)
api/apiv1/gen/control_plane/service.gois excluded by!**/gen/**api/apiv1/gen/http/openapi.jsonis excluded by!**/gen/**api/apiv1/gen/http/openapi.yamlis excluded by!**/gen/**api/apiv1/gen/http/openapi3.jsonis excluded by!**/gen/**api/apiv1/gen/http/openapi3.yamlis excluded by!**/gen/**
📒 Files selected for processing (23)
CHANGELOG.mdapi/version.txtchanges/unreleased/Added-20260504-150235.yamlchanges/unreleased/Added-20260511-090000.yamlchanges/unreleased/Added-20260511-090010.yamlchanges/unreleased/Added-20260511-090020.yamlchanges/unreleased/Added-20260511-100000.yamlchanges/unreleased/Added-20260610-000000.yamlchanges/unreleased/Added-20260611-090000.yamlchanges/unreleased/Added-20260611-090010.yamlchanges/unreleased/Changed-20260504-152348.yamlchanges/unreleased/Fixed-20260611-090000.yamlchanges/unreleased/Fixed-20260611-090010.yamlchanges/unreleased/Fixed-20260616-150152.yamlchanges/v0.9.0.mddocs/api/openapi.mddocs/api/reference.mddocs/changelog.mddocs/development/e2e-tests.mddocs/installation/installation.mddocs/installation/mtls.mddocs/installation/systemd.mddocs/installation/upgrading.md
💤 Files with no reviewable changes (12)
- changes/unreleased/Added-20260511-090010.yaml
- changes/unreleased/Fixed-20260616-150152.yaml
- changes/unreleased/Added-20260511-090020.yaml
- changes/unreleased/Added-20260511-090000.yaml
- changes/unreleased/Added-20260504-150235.yaml
- changes/unreleased/Added-20260610-000000.yaml
- changes/unreleased/Fixed-20260611-090010.yaml
- changes/unreleased/Added-20260611-090000.yaml
- changes/unreleased/Added-20260611-090010.yaml
- changes/unreleased/Fixed-20260611-090000.yaml
- changes/unreleased/Added-20260511-100000.yaml
- changes/unreleased/Changed-20260504-152348.yaml
This version got out of sync because of the merge order between the Debian support PR and the v0.8.1 patch release and, as a result, it didn't get updated automatically by the release target. This one-time manual change will get it back in sync.
On Debian, `server_version` contains build information, like: `18.4 (Debian 18.4-1.trixie)`. This breaks our process that reconciles the database spec with the observed Postgres version. This commit fixes that issue by changing our `GetPostgresVersion` query to use the integer representation of the server version, e.g. `180004`, to compute the string representation. This is more reliable and behaves consistently across host OSes.
We use `-y` in all the other `apt` and `dnf` commands so that they're easy to copy and paste or translate into a script.
Putting the Control Plane deb file in /tmp makes it accessible to the _apt user, so apt can avoid using the root user.
* fix: restart MCP container on KB config change KB config changes (path, provider, model, key) had no effect after an update: config.yaml is bind-mounted so SIGHUP-only reload kept the old KB path, causing "file not found" / SQLite errors. Embed a PGEDGE_CONFIG_VERSION hash in the MCP container env (like RAG) so a config change forces a restart and re-initializes the KB. Also refresh the service instance's UpdatedAt before an update redeploy so the monitor doesn't briefly mark it failed during the restart.
The preremove scriptlets also get called during package upgrade. Our preremove scriptlets stop and disable the control plane service, so we only want them to run during a removal. This commit resolves the issue by adding a condition that's only true during removal. This condition is different for each package type, so I've split this script into separate files like we do for the postinstall script.
Adds a migration for scheduled job dependencies to use the new common pgBackRest stanza resource type instead of the the old swarm one.
Adds validation to the backup database node endpoint to return a 400 error when the given node does not have a backup configuration.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This is the release PR for v0.9.0.