Skip to content

feat: release v0.3.1 - #39

Merged
bzp2010 merged 1 commit into
api7:mainfrom
janiussyafiq:release-v0.3.1
Aug 3, 2026
Merged

feat: release v0.3.1#39
bzp2010 merged 1 commit into
api7:mainfrom
janiussyafiq:release-v0.3.1

Conversation

@janiussyafiq

@janiussyafiq janiussyafiq commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Release v0.3.1.

0.3.0-0 pins 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; graphql (bare lpeg) and jsonpath (lpeg >= 1.0.0) then run against the downgraded global module. lpeg >= 1.0.2 lets APISIX keep the LPeg version it already resolves.

lua_pack is relaxed the same way — 2.0.0-0 is 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 main holds when this lands, so #38 should merge first for its fix to be in v0.3.1.

@coderabbitai

coderabbitai Bot commented Aug 3, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@janiussyafiq, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 44 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 Plus

Run ID: c4088eec-f2e9-4dba-84a3-2ad1f57e8c01

📥 Commits

Reviewing files that changed from the base of the PR and between 5eee1d9 and 31f7386.

📒 Files selected for processing (1)
  • rockspec/lua-resty-ldap-0.3.1-0.rockspec

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.

❤️ Share

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

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.
@bzp2010
bzp2010 merged commit 9b9be5b into api7:main Aug 3, 2026
3 checks passed
@janiussyafiq
janiussyafiq deleted the release-v0.3.1 branch August 3, 2026 06:15
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.

3 participants