chore(release): prepare v0.6.2 - #37
Conversation
Maintenance and dependency-security patch. No Portkey Admin API or MCP tool-surface changes; the 156-tool inventory holds at 156. - 🔒 close two medium ip-address advisories via the 10.4.0 bump - 📦 non-major npm bumps: biome 2.5.6, express-rate-limit 8.6.1, jose 6.2.7, knip 6.29.0, npm 11.19.0, redis 6.2.0 - 🔧 CI redis service moves to redis:8.8-alpine - 🗑️ drop the unused BaseService/validateUrl barrel re-exports
|
Warning Review limit reached
Next review available in: 48 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. 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: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe package version, server version, and packaged npm version were incremented from 🚥 Pre-merge checks | ✅ 2✅ Passed checks (2 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
biggest-littlest
left a comment
biggest-littlest
left a comment
There was a problem hiding this comment.
Version matches across package.json and both server.json fields, so auto-tag won't bail. Changelog reflects what actually landed. CI green.
ALARGECOMPANY
left a comment
ALARGECOMPANY
left a comment
There was a problem hiding this comment.
Release mechanics look right. Approved.
3 participants
Cuts v0.6.2 off the dependency and security work that landed today (#36, #33, #34). Patch-level: no Portkey Admin API changes, no MCP tool-surface changes, still 156 tools across 19 files.
What's in it
ip-address10.2.0 → 10.4.0, closing two medium advisories reachable throughexpress-rate-limit(CIDR-suffix special-use suppression, and IPv4-mapped/NAT64 misclassification). Both were SSRF and trust-boundary bypasses. Dependabot is now at zero open alerts.redis:8.8-alpine.BaseService/validateUrlbarrel re-exports.Version bump touches all three places
auto-tag.ymlchecks:package.json, and bothversionandpackages[0].versioninserver.json. They match at 0.6.2, so the tag job won't bail.Full
npm run cipasses locally. On merge, auto-tag cutsv0.6.2and dispatches the release workflow (npm publish via OIDC, GitHub Release, MCP Registry).Note: #35 (packageManager → npm 12) is still sitting in GitHub's runner queue and will land after this; it's dev tooling only and doesn't belong in the released artifact.
Changelog
ip-addressfrom10.2.0to10.4.0to fix two medium-severity advisories.express-rate-limit,jose, Knip, npm, and Redis.redis:8.8-alpine.BaseServiceandvalidateUrlbarrel re-exports.0.6.2.npm run cipasses locally.