docs: weekly changelog update - #294
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
Warning Review limit reached
More reviews will be available in 42 minutes and 39 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughAdds a single changelog entry for 2026-06-08 documenting API middleware standardization, Redis resilience testing, quota validation for bulk inserts, and multiple security/stability fixes; the existing 2026-06-01 section is left unchanged. ChangesChangelog Documentation Update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
There was a problem hiding this comment.
Pull request overview
Adds the auto-generated weekly changelog entry for the week of 2026-06-01–2026-06-08 to the Mintlify docs changelog, documenting recent improvements and bug fixes.
Changes:
- Added a new
<Update>section for 2026-06-08 with “Improvements” and “Bug fixes” entries. - Included changelog tags for the update to support categorization/filtering.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (2)
mintlify/docs/changelog/june-2026.mdx (2)
9-10: ⚡ Quick winApply code formatting to technical terms.
Per coding guidelines, use code formatting for technical references. The following terms should be formatted as code:
- Line 9:
Package-Middleware(component name)- Line 10:
503(HTTP status code),Redis(technology name)📝 Proposed formatting improvements
-**Standardized API Response** — Standardized the API Response in Package-Middleware to handle errors consistently (`#270`) -**Resilience Tests** — Added 503 resilience tests for Redis rejection paths to improve public API reliability (`#267`) +**Standardized API Response** — Standardized the API Response in `Package-Middleware` to handle errors consistently (`#270`) +**Resilience Tests** — Added `503` resilience tests for `Redis` rejection paths to improve public API reliability (`#267`)🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@mintlify/docs/changelog/june-2026.mdx` around lines 9 - 10, The changelog lines use plain text for technical terms; update the entries so technical references are formatted as inline code: wrap the component name Package-Middleware, the HTTP status code 503, and the technology name Redis in code formatting (e.g., `Package-Middleware`, `503`, `Redis`) in the two lines showing "Standardized API Response — Standardized the API Response in Package-Middleware..." and "Resilience Tests — Added 503 resilience tests for Redis rejection paths...".Source: Coding guidelines
17-22: ⚡ Quick winApply code formatting and bold UI elements per guidelines.
Multiple technical terms and code references are missing proper formatting:
- Line 17:
queryBuilder(code reference),2000(numeric limit)- Line 18:
AppError(class name)- Line 19:
file.originalname(code property),storage path(technical term)- Line 20:
isSafeUri(function name),RFC-1918(standard reference)- Line 21:
string(schema type); RLS owner dropdown should be bolded as a UI element- Line 22:
authLimiter(middleware name),OTP(technical acronym)📝 Proposed formatting improvements
-- Add 2000 character max-length guard on queryBuilder prompt to prevent excessive input (`#274`) -- Update error parsing to handle standardized AppError responses (`#273`) -- Sanitize file.originalname before use in storage path to prevent security vulnerabilities (`#275`) -- Expand isSafeUri to block RFC-1918 and cloud metadata IP ranges to improve security (`#256`) -- Show string schema fields in RLS owner dropdown to improve user experience (`#265`) -- Apply authLimiter to OTP and password reset routes to prevent abuse (`#264`) +- Add `2000` character max-length guard on `queryBuilder` prompt to prevent excessive input (`#274`) +- Update error parsing to handle standardized `AppError` responses (`#273`) +- Sanitize `file.originalname` before use in `storage path` to prevent security vulnerabilities (`#275`) +- Expand `isSafeUri` to block `RFC-1918` and cloud metadata IP ranges to improve security (`#256`) +- Show `string` schema fields in **RLS owner dropdown** to improve user experience (`#265`) +- Apply `authLimiter` to `OTP` and password reset routes to prevent abuse (`#264`)🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@mintlify/docs/changelog/june-2026.mdx` around lines 17 - 22, The changelog entries use plain text for technical identifiers and a UI element; update lines mentioning queryBuilder, 2000, AppError, file.originalname, storage path, isSafeUri, RFC-1918, string, authLimiter, and OTP to follow the style guide by wrapping code/technical identifiers and numeric limits in inline code formatting (e.g., `queryBuilder`, `2000`, `AppError`, `file.originalname`, `isSafeUri`, `RFC-1918`, `string`, `authLimiter`, `OTP`), bold the UI element "RLS owner dropdown" to **RLS owner dropdown**, and ensure phrases like "storage path" are formatted consistently as inline code or plain text per guidelines so the entries are uniformly styled.Source: Coding guidelines
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@mintlify/docs/changelog/june-2026.mdx`:
- Line 22: Update the changelog entry to reference the actual middleware used:
replace "authLimiter" with "checkUsageLimits" in the June 2026 changelog entry
so it reads "Apply checkUsageLimits to OTP and password reset routes to prevent
abuse (`#264`)"; reference the public auth routes (/resend-verification-otp,
/request-password-reset, /reset-password) and the middleware name
checkUsageLimits from apps/public-api/src/middlewares/usageGate.js to ensure
wording matches the implemented code (or alternatively document a separate
authLimiter if one exists elsewhere).
---
Nitpick comments:
In `@mintlify/docs/changelog/june-2026.mdx`:
- Around line 9-10: The changelog lines use plain text for technical terms;
update the entries so technical references are formatted as inline code: wrap
the component name Package-Middleware, the HTTP status code 503, and the
technology name Redis in code formatting (e.g., `Package-Middleware`, `503`,
`Redis`) in the two lines showing "Standardized API Response — Standardized the
API Response in Package-Middleware..." and "Resilience Tests — Added 503
resilience tests for Redis rejection paths...".
- Around line 17-22: The changelog entries use plain text for technical
identifiers and a UI element; update lines mentioning queryBuilder, 2000,
AppError, file.originalname, storage path, isSafeUri, RFC-1918, string,
authLimiter, and OTP to follow the style guide by wrapping code/technical
identifiers and numeric limits in inline code formatting (e.g., `queryBuilder`,
`2000`, `AppError`, `file.originalname`, `isSafeUri`, `RFC-1918`, `string`,
`authLimiter`, `OTP`), bold the UI element "RLS owner dropdown" to **RLS owner
dropdown**, and ensure phrases like "storage path" are formatted consistently as
inline code or plain text per guidelines so the entries are uniformly styled.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 32f8c7f7-87aa-45ee-8d20-21bd41417336
📒 Files selected for processing (1)
mintlify/docs/changelog/june-2026.mdx
|
Now I'll apply the formatting fixes. For comment about |
Generated-By: mintlify-agent
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Render
Destroyed
|
@Nitin-kumar-yadav1307 |
Auto-generated weekly changelog entry. Please review before merging.
Summary by CodeRabbit
New Features & Improvements
Bug Fixes & Security