docs: weekly changelog update 2026-05-25#211
Conversation
|
Warning Review limit reached
More reviews will be available in 58 minutes and 58 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)
📝 WalkthroughWalkthroughA new changelog entry (week 2026-05-18–2026-05-25) was added documenting Soft Delete & Trash Cleanup, feature section timeline and landing page UX improvements, and several bug fixes including AI Query Builder, login lockout retry handling, PR review fixes, and RLS-aware cURL examples. ChangesMay 2026 Changelog
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
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
Updates the Mintlify documentation changelog for May 2026 with a new weekly entry, documenting recent features, improvements, and fixes.
Changes:
- Added a new changelog
<Update>entry for 2026-05-25. - Documented new features (soft delete/trash cleanup), UI improvements, and several bug-fix PR references.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| <Update label="2026-05-25" description="Week of 2026-05-18–2026-05-25" tags={["Feature","Improvement","Fix"]}> | ||
| ## New features | ||
|
|
||
| **Soft Delete & Trash Cleanup** — Introduces a soft��delete mechanism for records and a background worker that permanently removes items from the trash after a configurable retention period. |
| description: What's new in urBackend — new features, improvements, and fixes for May. | ||
| --- | ||
|
|
||
| <Update label="2026-05-25" description="Week of 2026-05-18–2026-05-25" tags={["Feature","Improvement","Fix"]}> |
| description: What's new in urBackend — new features, improvements, and fixes for May. | ||
| --- | ||
|
|
||
| <Update label="2026-05-25" description="Week of 2026-05-18–2026-05-25" tags={["Feature","Improvement","Fix"]}> |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 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/may-2026.mdx`:
- Line 22: Update the changelog bullet "Make database empty‑state cURL snippet
RLS‑aware to avoid 403 errors (`#190`)" to use inline code formatting for the
command/code references: wrap `cURL`, `RLS`, and `403` in backticks so they
appear as code spans in the docs.
- Line 9: The sentence contains a corrupted character sequence in "soft��delete"
and uses third-person phrasing; replace the broken sequence with "soft delete"
and rewrite the sentence in active second-person voice so it addresses the
reader—e.g., change the line under "Soft Delete & Trash Cleanup" to something
like "You can soft delete records, and a background worker permanently removes
items from the trash after a configurable retention period," ensuring plain
ASCII for "soft delete" and preserving the feature name "Soft Delete & Trash
Cleanup."
- Line 9: Update the changelog line under "Soft Delete & Trash Cleanup" to
reflect the actual behavior: change "a background worker that permanently
removes items from the trash after a configurable retention period" to indicate
a fixed 30-day retention (e.g., "after a fixed 30-day retention period"), or
alternatively, if there is an exposed configuration, reference the exact
configuration symbol (the background worker and its retention setting) where
configurability is implemented; ensure the phrasing matches the implementation
used by the background worker/trash cleanup logic.
🪄 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: 4954a1dc-c142-4faf-a588-cc7d872d1efd
📒 Files selected for processing (1)
mintlify/docs/changelog/may-2026.mdx
Generated-By: mintlify-agent
Generated-By: mintlify-agent
|
Wrapped cURL, RLS, and 403 in backticks on the bug fix line; line 9 already used clean "soft-delete" and the 30-day retention wording, so no further changes were needed. |
chagelog
Summary by CodeRabbit
New Features
Bug Fixes