Skip to content

chore(main): release 1.6.0#10

Open
HyperSoWeak wants to merge 1 commit into
mainfrom
release-please--branches--main--components--yuzu-bot
Open

chore(main): release 1.6.0#10
HyperSoWeak wants to merge 1 commit into
mainfrom
release-please--branches--main--components--yuzu-bot

Conversation

@HyperSoWeak

@HyperSoWeak HyperSoWeak commented May 25, 2026

Copy link
Copy Markdown
Owner

🤖 I have created a release beep boop

1.6.0 (2026-05-28)

Features

  • backup: add optional Google Drive upload via rclone (6aa2a4d)
  • backup: send Discord notification on backup completion (6d043ba)
  • mine: persist active games across restarts (d4f101e)
  • mine: replace per-player move cap with 5-step consecutive limit (4308371)
  • role-menu: replace reaction-role with button-only role-menu (e8a7069)
  • role-menu: replace reaction-role with button-only role-menu (0baded3)

Bug Fixes

  • role-menu: fix TOCTOU race in getOrCreateMenu using upsert (fbb4fb5)
  • role-menu: replace deprecated ephemeral:true with MessageFlags.Ephemeral (52e32ec)

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

  • New Features

    • Google Drive backup support via rclone
    • Discord notifications on backup completion
    • Mine games persistence across restarts
    • Updated mine move limit to 5-step consecutive format
    • Switched role-menu to button-based interface
  • Bug Fixes

    • Fixed role-menu race condition issue
    • Updated message flag handling

Review Change Stack

@HyperSoWeak HyperSoWeak force-pushed the release-please--branches--main--components--yuzu-bot branch 3 times, most recently from de70373 to d304e70 Compare May 26, 2026 07:40
@coderabbitai

coderabbitai Bot commented May 26, 2026

Copy link
Copy Markdown

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: a271424e-0d44-4ad6-a163-eda6080495a6

📥 Commits

Reviewing files that changed from the base of the PR and between c2d0ced and c1e7c4f.

📒 Files selected for processing (3)
  • .release-please-manifest.json
  • CHANGELOG.md
  • package.json
✅ Files skipped from review due to trivial changes (3)
  • .release-please-manifest.json
  • package.json
  • CHANGELOG.md

📝 Walkthrough

Walkthrough

Bumps project version from 1.5.0 to 1.6.0 in package.json and .release-please-manifest.json, and inserts a new ## [1.6.0] entry at the top of CHANGELOG.md listing Features and Bug Fixes.

Changes

Version 1.6.0 Release

Layer / File(s) Summary
Version sync and changelog
package.json, .release-please-manifest.json, CHANGELOG.md
Project version updated from 1.5.0 to 1.6.0 in package.json and .release-please-manifest.json; CHANGELOG.md receives a new ## [1.6.0] entry with Features and Bug Fixes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A hop, a bump—one point six we see,
package and manifest in harmony,
Changelog whispers what's now brand new,
A tiny release, a cheerful view.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'chore(main): release 1.6.0' clearly and concisely summarizes the main change - creating a release for version 1.6.0. It aligns with the changeset which updates version numbers across configuration files and adds release notes.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release-please--branches--main--components--yuzu-bot

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

@coderabbitai coderabbitai 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.

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 11-12: Duplicate changelog entry "**role-menu:** replace
reaction-role with button-only role-menu" appears twice (commits e8a7069 and
0baded3); edit CHANGELOG.md to consolidate into a single entry for that feature
and either list both commit hashes in the same line or keep the most relevant
commit hash (remove the other duplicate), ensuring the final line still contains
the descriptive text and at least one commit reference.
🪄 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 Plus

Run ID: c7a7b6d4-bbed-4cc5-be7f-916c9857a669

📥 Commits

Reviewing files that changed from the base of the PR and between e8a7069 and d304e70.

📒 Files selected for processing (3)
  • .release-please-manifest.json
  • CHANGELOG.md
  • package.json

Comment thread CHANGELOG.md
Comment on lines +11 to +12
* **role-menu:** replace reaction-role with button-only role-menu ([e8a7069](https://github.com/HyperSoWeak/yuzu-bot/commit/e8a7069b9de69b47d43a3d8b9d4b6d9edc7ca3a1))
* **role-menu:** replace reaction-role with button-only role-menu ([0baded3](https://github.com/HyperSoWeak/yuzu-bot/commit/0baded3987ac4413a000e32183e7543a5cf21747))

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Duplicate feature entry in changelog.

The same feature description appears twice with different commit hashes. This may confuse readers of the changelog. Consider consolidating these entries or clarifying why the same feature appears twice.

🤖 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 11 - 12, Duplicate changelog entry "**role-menu:**
replace reaction-role with button-only role-menu" appears twice (commits e8a7069
and 0baded3); edit CHANGELOG.md to consolidate into a single entry for that
feature and either list both commit hashes in the same line or keep the most
relevant commit hash (remove the other duplicate), ensuring the final line still
contains the descriptive text and at least one commit reference.

@HyperSoWeak HyperSoWeak force-pushed the release-please--branches--main--components--yuzu-bot branch from d304e70 to c2d0ced Compare May 28, 2026 10:01
@HyperSoWeak HyperSoWeak force-pushed the release-please--branches--main--components--yuzu-bot branch from c2d0ced to c1e7c4f Compare May 28, 2026 13:58
@coderabbitai

coderabbitai Bot commented May 28, 2026

Copy link
Copy Markdown

Actionable comments posted: 0

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