Skip to content

chore(main): release 0.1.77#54

Merged
bhekanik merged 2 commits into
mainfrom
release-please--branches--main--components--spotuify
Jul 11, 2026
Merged

chore(main): release 0.1.77#54
bhekanik merged 2 commits into
mainfrom
release-please--branches--main--components--spotuify

Conversation

@bhekanik

@bhekanik bhekanik commented Jul 11, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.1.77 (2026-07-11)

Features

  • add desktop theme setting (system/light/dark/adaptive) (#51) (94b7706)
  • lazy-load liked songs with scroll pagination (#52) (c395943)
  • play liked songs track within full collection context (#55) (be5b50d)

This PR was generated with Release Please. See documentation.

@vercel

vercel Bot commented Jul 11, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
spotuify Ready Ready Preview, Comment Jul 11, 2026 2:39am

@coderabbitai

coderabbitai Bot commented Jul 11, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@bhekanik, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 52 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 8d3415f9-e07f-4f18-b0b7-c903d4f94602

📥 Commits

Reviewing files that changed from the base of the PR and between be5b50d and 10e4407.

⛔ Files ignored due to path filters (1)
  • Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (3)
  • .release-please-manifest.json
  • CHANGELOG.md
  • Cargo.toml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release-please--branches--main--components--spotuify

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 4 files

Re-trigger cubic

@bhekanik bhekanik force-pushed the release-please--branches--main--components--spotuify branch from 882e120 to 36fd801 Compare July 11, 2026 02:24
@bhekanik bhekanik force-pushed the release-please--branches--main--components--spotuify branch from 7bc27b8 to d410f46 Compare July 11, 2026 02:38
@bhekanik bhekanik merged commit 4c6613f into main Jul 11, 2026
21 of 23 checks passed
@bhekanik

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant