chore: release v1.6.0#205
Conversation
|
🚅 Deployed to the reqcore-pr-205 environment in applirank
|
JoachimLK
force-pushed
the
release-please--branches--main--components--reqcore
branch
from
2afd22f to
1b675da
Compare
|
Warning Review limit reached
Next review available in: 45 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. 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: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (3)
📝 WalkthroughWalkthroughVersion metadata was bumped to ChangesRelease 1.6.0 version bump
Estimated code review effort: 1 (Trivial) | ~2 minutes 🚥 Pre-merge checks | ✅ 1 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (1 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 |
JoachimLK
force-pushed
the
release-please--branches--main--components--reqcore
branch
from
1b675da to
43ba546
Compare
![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
🤖 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 `@CHANGELOG.md`:
- Around line 28-29: The CHANGELOG.md file contains duplicate entries for the
same features: lines 28-29 both document "enforce demo account isolation and
organization access restrictions" with different commit hashes, and lines 34-35
both document "implement candidate erasure service and GDPR retention logic"
with different commit hashes. Remove one of each duplicate pair by keeping only
a single entry per feature. Verify which commit hash is correct for each feature
and retain that entry, then delete the duplicate line to consolidate the
changelog.
🪄 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: bde4b04d-f81b-4cd5-a525-5731ad78b50d
📥 Commits
Reviewing files that changed from the base of the PR and between 1b675da6753b1d8959594d71152732effeea2f6b and 43ba546.
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (3)
.release-please-manifest.jsonCHANGELOG.mdpackage.json
✅ Files skipped from review due to trivial changes (2)
- .release-please-manifest.json
- package.json
| * enforce demo account isolation and organization access restrictions ([f47296e](https://github.com/reqcore-inc/reqcore/commit/f47296e91bcc3dad116d25152d8791a7d999c054)) | ||
| * enforce demo account isolation and organization access restrictions ([72433b9](https://github.com/reqcore-inc/reqcore/commit/72433b9c23bc0a9aaa28c03db36c97e86f01e0cf)) |
There was a problem hiding this comment.
Remove duplicate changelog entries.
Lines 28–29 both document "enforce demo account isolation and organization access restrictions" with different commit hashes. Similarly, lines 34–35 both document "implement candidate erasure service and GDPR retention logic" with different commit hashes. These appear to be duplicate entries that should be consolidated. Verify which commit(s) should be retained for each feature.
💡 Suggested fix (remove one of each pair)
* enforce demo account isolation and organization access restrictions ([f47296e](https://github.com/reqcore-inc/reqcore/commit/f47296e91bcc3dad116d25152d8791a7d999c054))
-* enforce demo account isolation and organization access restrictions ([72433b9](https://github.com/reqcore-inc/reqcore/commit/72433b9c23bc0a9aaa28c03db36c97e86f01e0cf))
* enhance GDPR retention and erasure processes with improved confirmation and settings ([6e110c3](https://github.com/reqcore-inc/reqcore/commit/6e110c36fe007b131080025a2bb4c3b147091370))and
* implement candidate erasure service and GDPR retention logic ([8692040](https://github.com/reqcore-inc/reqcore/commit/869204063470a88b060b03a33f353250545291ac))
-* implement candidate erasure service and GDPR retention logic ([b2910f8](https://github.com/reqcore-inc/reqcore/commit/b2910f8592b8a92936076c494f6710c5c11f7a79))
* implement candidate retention and erasure processes ([7ee6ee3](https://github.com/reqcore-inc/reqcore/commit/7ee6ee315a1c9293e1777f8f1992b486fbda1085))Also applies to: 34-35
🤖 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 `@CHANGELOG.md` around lines 28 - 29, The CHANGELOG.md file contains duplicate
entries for the same features: lines 28-29 both document "enforce demo account
isolation and organization access restrictions" with different commit hashes,
and lines 34-35 both document "implement candidate erasure service and GDPR
retention logic" with different commit hashes. Remove one of each duplicate pair
by keeping only a single entry per feature. Verify which commit hash is correct
for each feature and retain that entry, then delete the duplicate line to
consolidate the changelog.
43ba546 to
81361ed
Compare
railway-app
Bot
requested a deployment
to
applirank / reqcore-pr-205
|
Caution Review failedAn error occurred during the review process. Please try again later. 📝 WalkthroughWalkthroughVersion bumped from ChangesRelease 1.6.0 version bump
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Suggested labels
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Note 🎁 Summarized by CodeRabbit FreeThe PR author is not assigned a seat. To perform a comprehensive line-by-line review, please assign a seat to the pull request author through the subscription management page by visiting https://app.coderabbit.ai/login. Comment |
JoachimLK
force-pushed
the
release-please--branches--main--components--reqcore
branch
from
81361ed to
0db4606
Compare
JoachimLK
force-pushed
the
release-please--branches--main--components--reqcore
branch
from
0db4606 to
da4b0c1
Compare
JoachimLK
force-pushed
the
release-please--branches--main--components--reqcore
branch
from
da4b0c1 to
506e8ea
Compare
1 participant
🤖 I have created a release beep boop
1.6.0 (2026-07-03)
✨ Features
🐛 Bug Fixes
♻️ Refactoring
🧪 Testing
🏗️ Build & CI
This PR was generated with Release Please. See documentation.