chore(seanime-extensions): release 0.9.0#26
Conversation
22514e9 to
702b8b6
Compare
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 55 minutes Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab. 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: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (6)
Walkthrough
Changesv0.9.0 Release Bump
Estimated code review effort: 1 (Trivial) | ~2 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
702b8b6 to
c318faa
Compare
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 `@packages/seanime-extensions/CHANGELOG.md`:
- Around line 3-21: The CHANGELOG.md file for version 0.9.0 contains broken
commit links that reference commit SHAs (9109cf1, db6e5e4, 0de2a55, 65e6d78,
b28201b, 81093f5) that do not exist in the IbbyLabs/AIOS repository. Verify the
correct commit SHAs from the actual repository where these changes exist
(potentially Viren070/AIOStreams or another source repository), then update each
commit SHA reference in the Features and Bug Fixes sections of the 0.9.0 entry
to link to the correct repository and valid commit hashes. Alternatively, if
using Release Please for automated changelog generation, regenerate the
changelog with the correct repository configuration before publishing the 0.9.0
release.
🪄 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: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: fe0cb79e-a485-4661-a29c-2c4769d92ebd
📒 Files selected for processing (6)
.release-please-manifest.jsonpackages/seanime-extensions/CHANGELOG.mdpackages/seanime-extensions/package.jsonpackages/seanime-extensions/src/extensions/aiostreams-plugin/manifest.jsonpackages/seanime-extensions/src/extensions/aiostreams-torrent-provider/manifest.jsonpackages/seanime-extensions/src/extensions/stremio-custom-source/manifest.json
📜 Review details
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: test
🔇 Additional comments (5)
packages/seanime-extensions/package.json (1)
4-4: LGTM!.release-please-manifest.json (1)
3-3: LGTM!packages/seanime-extensions/src/extensions/aiostreams-plugin/manifest.json (1)
4-4: LGTM!packages/seanime-extensions/src/extensions/aiostreams-torrent-provider/manifest.json (1)
4-4: LGTM!packages/seanime-extensions/src/extensions/stremio-custom-source/manifest.json (1)
4-4: LGTM!
c318faa to
028b5dd
Compare
028b5dd to
82a82c2
Compare
82a82c2 to
5e192c0
Compare
🤖 I have created a release beep boop
0.9.0 (2026-07-01)
Features
Bug Fixes
This PR was generated with Release Please. See documentation.