chore: release 2.3.0#21
Merged
Merged
Conversation
SINENSIA
approved these changes
May 10, 2026
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
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
Cuts the 2.3.0 release after three additive features merged since 2.2.0 (allowlist override, rate limiting, SBOM workflow). All changes are backward-compatible, hence a minor bump.
Changes in this PR
package.json→2.3.0.openapi.json→info.version: "2.3.0"(the contract test enforces the sync).CHANGELOG.md: the fourUnreleasedentries are promoted under## [2.3.0] - 2026-05-10, and the link list at the bottom is updated.What's in 2.3.0
ALLOWLIST_FILE(refactor: extract allowlist to lib/ with ALLOWLIST_FILE override #18).RATE_LIMIT_RPM(feat: opt-in per-IP rate limiting on /validate via RATE_LIMIT_RPM #19).Test plan
npm test— 48/48 (the version-sync test confirmsopenapi.jsonmatchespackage.json).v2.3.0, create the GitHub Release using the 2.3.0 CHANGELOG section. The new SBOM workflow will trigger automatically and attachsbom.cdx.jsonto the release.v2.2.0viaActions → SBOM → Run workflow → tag: v2.2.0.