feat: release v0.3.1 - #39
Conversation
|
Warning Review limit reached
Next review available in: 44 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)
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 |
Relax the dependency pins to ranges so consumers keep their own resolved versions. 0.3.0 pinned `lpeg = 1.0.2-1`. In a clean APISIX dependency tree that exact pin removes the resolved lpeg 1.1.0-2 and installs 1.0.2, and `graphql` and `jsonpath` — which ask for bare `lpeg` and `lpeg >= 1.0.0` — then run against the downgraded global module. `lpeg >= 1.0.2` keeps APISIX on the version it already resolves. `lua_pack` gets the same treatment for the same reason; 2.0.0-0 is still the newest, so it resolves identically today.
88eace0 to
31f7386
Compare
Release v0.3.1.
0.3.0-0pinslpeg = 1.0.2-1. In a clean APISIX dependency tree that exact pin removes the resolvedlpeg 1.1.0-2and installs1.0.2;graphql(barelpeg) andjsonpath(lpeg >= 1.0.0) then run against the downgraded global module.lpeg >= 1.0.2lets APISIX keep the LPeg version it already resolves.lua_packis relaxed the same way —2.0.0-0is still the newest, so it resolves identically today.Resolves the dependency-pin comment on apache/apisix#13762.
Note on sequencing: the release workflow tags whatever
mainholds when this lands, so #38 should merge first for its fix to be in v0.3.1.