Repository navigation
chore(release): v2.6.66 - #509
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
added
dependencies
📝 WalkthroughWalkthroughVersion release 2.6.66 documenting consolidation of embed construction utilities and refactoring of music/engagement commands to use shared helpers for consistent embed formatting across Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested labels
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 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 |
|
Size Change: 0 B Total Size: 324 kB ℹ️ View Unchanged
|
![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 the current code and only fix it if needed.
Inline comments:
In `@CHANGELOG.md`:
- Around line 10-25: The 2.6.66 changelog entry is missing explicit PR/issue
references; update the "## [2.6.66] - 2026-04-09" section by appending the
relevant PR and issue IDs for each notable change (for example link the PR that
added buildCommandTrackEmbed and the PR that refactored shared embed builders),
and add a short "Breaking Changes" subsection if any change is breaking;
reference the unique symbols to locate changes (buildCommandTrackEmbed,
buildTrackEmbed, createQueueEmbed, /pause, /resume, /skip, /songinfo, /level
leaderboard) and format each bullet to include "PR #<num>" and "Issue #<num>"
next to the related bullet.
🪄 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: CHILL
Plan: Pro
Run ID: fbbd18a9-bd36-49c9-b0df-7e466567bbe0
📒 Files selected for processing (6)
CHANGELOG.mdpackage.jsonpackages/backend/package.jsonpackages/bot/package.jsonpackages/frontend/package.jsonpackages/shared/package.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). (3)
- GitHub Check: Quality Gates
- GitHub Check: SonarCloud Scan
- GitHub Check: compressed-size
🧰 Additional context used
📓 Path-based instructions (11)
{LICENSE,COPYING,COPYING.md,LICENSE.md,license.txt,**/package.json,**/requirements.txt,**/Cargo.toml,**/pom.xml,**/composer.json}
📄 CodeRabbit inference engine (.cursor/rules/accessibility-openness.mdc)
Respect OSS licenses for third-party code and declare license in repo
Files:
packages/shared/package.jsonpackages/backend/package.jsonpackages/bot/package.jsonpackages/frontend/package.jsonpackage.json
packages/shared/package.json
📄 CodeRabbit inference engine (.cursor/rules/lucky-project.mdc)
The
sharedpackage must not have dependencies on bot or backend packages, only provide config, services (DB/Redis), types, and utils
Files:
packages/shared/package.json
packages/shared/**/*
📄 CodeRabbit inference engine (.cursor/rules/subagent-data.mdc)
Shared client and services must be located in
packages/shared
Files:
packages/shared/package.json
packages/backend/**
📄 CodeRabbit inference engine (.cursor/rules/lucky-project.mdc)
The
backendpackage depends onsharedand contains Express API with auth and guild routes
Files:
packages/backend/package.json
packages/bot/**
📄 CodeRabbit inference engine (.cursor/rules/lucky-project.mdc)
The
botpackage depends onsharedand contains Discord bot commands and player handlers using Discord.js and Discord Player
Files:
packages/bot/package.json
packages/frontend/**
📄 CodeRabbit inference engine (.cursor/rules/lucky-project.mdc)
The
frontendpackage uses React with Vite and must not depend on the shared package
Files:
packages/frontend/package.json
{webpack.config.{js,ts},vite.config.{js,ts},esbuild.config.{js,ts},package.json,.bundlebudgetrc,.bundlebudgetrc.json}
📄 CodeRabbit inference engine (.cursor/rules/performance-observability.mdc)
Add performance budgets for frontend bundles
Files:
package.json
package.json
📄 CodeRabbit inference engine (.cursor/rules/lucky-project.mdc)
package.json: Use npm workspaces monorepo structure with packages inpackages/*directory containing:shared(config, services, types, utils),bot(Discord.js/Discord Player),backend(Express API), andfrontend(React/Vite)
Usenpm run buildfor shared → bot → backend build order; usenpm run build:frontendseparately for frontend
Usenpm run dev:bot,npm run dev:backend, andnpm run dev:frontendfor development, andnpm run db:*commands for database operations
Files:
package.json
{CHANGELOG.md,README.md}
📄 CodeRabbit inference engine (.cursor/rules/agent-rules.mdc)
ALWAYS update CHANGELOG.md and README.md as changes are made.
Files:
CHANGELOG.md
CHANGELOG.md
📄 CodeRabbit inference engine (.cursor/rules/templates-examples.mdc)
CHANGELOG.md must be updated with all changes in pull requests
Always update CHANGELOG.md with all code changes
Update CHANGELOG.md with all changes, include breaking changes documentation, and reference issues and PRs
Files:
CHANGELOG.md
{CHANGELOG.md,docs/**}
📄 CodeRabbit inference engine (.cursor/rules/lucky-project.mdc)
Update
CHANGELOG.mdand relevantdocs/files when behavior or setup changes
Files:
CHANGELOG.md
🔇 Additional comments (5)
packages/shared/package.json (1)
3-3: Version bump is clean and scoped.
@lucky/sharedrelease version update is consistent and does not alter shared package boundaries.packages/bot/package.json (1)
3-3: Release version update looks good.The package version bump is consistent with the monorepo release tagging for
2.6.66.packages/backend/package.json (1)
3-3: Backend package version bump is correct.No additional concerns on this segment.
package.json (1)
3-3: Root version bump is aligned with workspace release.This change is straightforward and consistent with sibling package bumps.
packages/frontend/package.json (1)
4-4: Frontend package version bump is good.No functional or packaging concerns in this change.
| ## [2.6.66] - 2026-04-09 | ||
|
|
||
| ### Added | ||
|
|
||
| - **`buildCommandTrackEmbed` helper** (`packages/bot/src/utils/general/responseEmbeds/buildTrackEmbed.ts`): combines `trackToData + buildTrackEmbed + setAuthor` into a single call. Used by `pause`, `resume`, and `skip` commands to display a rich track embed with a custom status label (e.g. "⏸️ Paused", "▶️ Resumed", "⏭️ Song skipped") as the embed author. | ||
| - **Shared embed builder utilities** (`packages/bot/src/utils/general/responseEmbeds/`): `buildTrackEmbed`, `buildUserProfileEmbed`, `buildListPageEmbed`, `buildPlatformAttribEmbed` — reusable embed constructors shared across commands. Embed functions in `embeds.ts` unified to `createSuccessEmbed`, `createErrorEmbed`, `createInfoEmbed`, `createWarningEmbed`. | ||
|
|
||
| ### Changed | ||
|
|
||
| - **`/pause`, `/resume`, `/skip` commands**: show a rich track embed (title, thumbnail, duration, platform badge, requester footer) instead of a plain text success message when a track is active. | ||
| - **`/songinfo` command**: migrated to `buildTrackEmbed` + `trackToData`, removing the legacy inline embed builder. | ||
| - **`/level leaderboard`**: results are now paginated (5 entries per page) with prev/next buttons, preventing Discord embed field truncation for guilds with many members. Fetches up to 50 entries via `levelService.getLeaderboard(guildId, 50)`. | ||
| - **Queue embed** (`/queue` command): rebuilt with `createQueueEmbed` — structured sections for now-playing, upcoming tracks, queue stats, and music controls, all consistent with shared embed patterns. | ||
| - **Engagement commands** (`/starboard`, `/lastfm`): migrated to shared embed builders (`buildListPageEmbed`, `buildPlatformAttribEmbed`, `createSuccessEmbed/createErrorEmbed/createInfoEmbed`). | ||
| - **Autoplay embed** (`/play` now-playing): added `.setTimestamp()` to embed builder for consistent timestamp display. Error handler for the `play` command now uses `createErrorEmbed`. | ||
|
|
There was a problem hiding this comment.
Add explicit PR/issue references in the 2.6.66 entry.
The release notes are detailed, but this section should include direct references (e.g., PR #509``, related issue IDs) to satisfy changelog traceability requirements.
As per coding guidelines, "Update CHANGELOG.md with all changes, include breaking changes documentation, and reference issues and PRs".
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@CHANGELOG.md` around lines 10 - 25, The 2.6.66 changelog entry is missing
explicit PR/issue references; update the "## [2.6.66] - 2026-04-09" section by
appending the relevant PR and issue IDs for each notable change (for example
link the PR that added buildCommandTrackEmbed and the PR that refactored shared
embed builders), and add a short "Breaking Changes" subsection if any change is
breaking; reference the unique symbols to locate changes
(buildCommandTrackEmbed, buildTrackEmbed, createQueueEmbed, /pause, /resume,
/skip, /songinfo, /level leaderboard) and format each bullet to include "PR
#<num>" and "Issue #<num>" next to the related bullet.
|
This branch was successfully deployed
1 participant
Summary
/level leaderboard(5 entries/page with prev/next buttons)/pause,/resume,/skip,/songinfoviabuildCommandTrackEmbedhelperbuildTrackEmbed,buildUserProfileEmbed,buildListPageEmbed,buildPlatformAttribEmbed) across all commandscreateSuccessEmbed,createErrorEmbed,createInfoEmbed,createWarningEmbed)Test plan
🤖 Generated with Claude Code
Summary by CodeRabbit
Release Notes v2.6.66
New Features
/level leaderboard(5 entries per page with navigation controls)./pause,/resume,/skip, and/playcommands with rich track embeds./queue,/songinfo,/starboard, and/lastfmcommands.Bug Fixes