Skip to content

release(aisix-cp): 0.6.0 - #326

Merged
nic-6443 merged 1 commit into
mainfrom
release-aisix-cp-0.6.0
Jul 29, 2026
Merged

release(aisix-cp): 0.6.0#326
nic-6443 merged 1 commit into
mainfrom
release-aisix-cp-0.6.0

Conversation

@jarvis9443

Copy link
Copy Markdown
Contributor

Releases aisix-cp 0.6.0.

Changes

  • Chart.yaml: version and appVersion0.6.0
  • README.md: regenerated by helm-docs (version badges)

No template or values changes. The accumulated delta from the development chart — the cp-api and dp-manager startup probes — already shipped in the 0.5.1 chart-only patch, so this cycle has no functional chart change left to sync. The residual diff against the source-of-truth chart (control-plane/helm/aisix-cp) is only the intentional public adaptations: docker.io registries, empty image tags resolving to .Chart.AppVersion, the api.dpImage default, and this README.

Images

appVersion pins the image tags, and all four are published:

  • docker.io/api7/aisix-cp-api:0.6.0
  • docker.io/api7/aisix-cp-dpm:0.6.0
  • docker.io/api7/aisix-cp-ui:0.6.0
  • docker.io/api7/aisix:0.6.0 (the api.dpImage default)

Merging publishes aisix-cp-0.6.0 to https://charts.api7.ai and rolls the POC environment onto 0.6.0.

Bumps version and appVersion to 0.6.0 and regenerates the README.

The 0.5.1 chart-only patch already carried the accumulated template delta (the cp-api and dp-manager startup probes), so this release has no functional chart change to sync: the residual diff against control-plane/helm/aisix-cp is only the public adaptations (docker.io registries, empty image tags resolving to .Chart.AppVersion, the api.dpImage default, and the generated README).

appVersion pins the image tags, and docker.io/api7/aisix-cp-{api,dpm,ui}:0.6.0 plus docker.io/api7/aisix:0.6.0 are published.
@coderabbitai

coderabbitai Bot commented Jul 29, 2026

Copy link
Copy Markdown

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 19 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: 98e7270e-0a73-4e22-870b-211c846c4b18

📥 Commits

Reviewing files that changed from the base of the PR and between f20d1b4 and b462cef.

📒 Files selected for processing (2)
  • charts/aisix-cp/Chart.yaml
  • charts/aisix-cp/README.md

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

@nic-6443
nic-6443 merged commit af34816 into main Jul 29, 2026
3 checks passed
@nic-6443
nic-6443 deleted the release-aisix-cp-0.6.0 branch July 29, 2026 07:32
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.

2 participants