Skip to content

release(aisix-cp): 0.4.0#321

Merged
nic-6443 merged 1 commit into
mainfrom
release-aisix-cp-0.4.0
Jul 16, 2026
Merged

release(aisix-cp): 0.4.0#321
nic-6443 merged 1 commit into
mainfrom
release-aisix-cp-0.4.0

Conversation

@jarvis9443

Copy link
Copy Markdown
Contributor

Release the public aisix-cp chart at 0.4.0.

  • Bump version and appVersion to 0.4.0; regenerate README.md.
  • Version-only release sync: the source-of-truth chart (control-plane/helm/aisix-cp) had no functional changes since 0.3.1, so no template/values deltas are ported this cycle.
  • Preserves the public adaptations: docker.io registries, tag: "".Chart.AppVersion, always-emit api.dpImage default → docker.io/api7/aisix:<appVersion>, and README.md.

helm lint clean; helm template renders aisix-cp-{api,dpm,ui}:0.4.0 and AISIX_CLOUD_DP_IMAGE=docker.io/api7/aisix:0.4.0, with the dpm /healthz probes intact.

Merging publishes aisix-cp-0.4.0 to https://charts.api7.ai. The pinned images (docker.io/api7/aisix:0.4.0 and docker.io/api7/aisix-cp-{api,dpm,ui}:0.4.0) are already published.

Version-only release sync: bump version and appVersion to 0.4.0 and regenerate README. The CP source-of-truth chart (control-plane/helm/aisix-cp) had no functional changes since 0.3.1, so no template/values deltas are ported this cycle. Public adaptations (docker.io registries, tag -> .Chart.AppVersion, always-emit api.dpImage default, README) are preserved.
@coderabbitai

coderabbitai Bot commented Jul 16, 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: 12 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: c03e616d-5fec-414d-aa40-f886fb7ad3a8

📥 Commits

Reviewing files that changed from the base of the PR and between 19d2da2 and 4ae89be.

📒 Files selected for processing (2)
  • charts/aisix-cp/Chart.yaml
  • charts/aisix-cp/README.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release-aisix-cp-0.4.0

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

@nic-6443
nic-6443 merged commit 794c9cc into main Jul 16, 2026
3 checks passed
@nic-6443
nic-6443 deleted the release-aisix-cp-0.4.0 branch July 16, 2026 05:37
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