aurora-rgb: Add version 325
Your changes do not pass checks.
aurora-rgb
- [x] Description
- [x] License
- [x] Hashes
- [ ] Checkver
- [ ] Autoupdate
/verify
Your changes do not pass checks.
aurora-rgb
- [x] Description
- [x] License
- [x] Hashes
- [ ] Checkver
- [ ] Autoupdate
/verify
All changes look good.
Wait for review from human collaborators.
aurora-rgb
- [x] Description
- [x] License
- [x] Hashes
- [x] Checkver
- [x] Autoupdate
why is this not merged yet? current version of aurora on extras bucket is outdated by 5 years (last updated on 2020)
Walkthrough
Adds a new Scoop manifest bucket/aurora-rgb.json defining Aurora RGB v350: metadata, 64-bit download URL with SHA-256, a shortcut mapping, GitHub-based checkver, and an autoupdate URL template using the version variable.
Changes
| Cohort / File(s) | Summary |
|---|---|
New Scoop manifestbucket/aurora-rgb.json |
Added Aurora RGB package manifest: version 350; 64-bit url and sha256; shortcuts mapping launcher to friendly name; checkver from GitHub; autoupdate 64-bit URL template using $version. |
Estimated code review effort
🎯 2 (Simple) | ⏱️ ~8 minutes
Poem
I thump my paws—new lights to see,
Aurora hums in RGB.
A hash, a URL, tidy and free,
The bucket blooms with version three-five-oh glee.
Hop, install, glow—bun-approved spree. 🐰✨
Pre-merge checks and finishing touches
❌ Failed checks (1 warning)
| Check name | Status | Explanation | Resolution |
|---|---|---|---|
| Description Check | ⚠️ Warning | The description provides a clear summary of adding version 350 and includes the correct “Closes” reference to the relevant issue along with confirmation of reading the Contributing Guide, but it omits the first required checklist item for confirming the use of a conventional PR title. This missing checkbox means the template is not fully adhered to. To fully comply with the repository’s description guidelines, that missing checklist item should be added. | Please add the missing checklist item “- [ ] Use conventional PR title: `<manifest-name[@version] |
✅ Passed checks (2 passed)
| Check name | Status | Explanation |
|---|---|---|
| Title Check | ✅ Passed | The title “aurora-rgb: Add version 350” clearly follows the required <manifest-name>: <general summary> pattern and succinctly references the key change of introducing version 350. It avoids unnecessary noise and provides immediate clarity on the update being made. This concise phrasing allows maintainers to understand the pull request’s intent at a glance. |
| Docstring Coverage | ✅ Passed | No functions found in the changes. Docstring coverage check skipped. |
✨ Finishing touches
🧪 Generate unit tests
- [ ] Create PR with unit tests
- [ ] Post copyable unit tests in a comment
📜 Recent review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📥 Commits
Reviewing files that changed from the base of the PR and between aa15f16b7f252dba85cc43c1b55b0bc61d41948d and 63359791d804f3be5751bad895b824049062d036.
📒 Files selected for processing (1)
bucket/aurora-rgb.json(1 hunks)
🔇 Additional comments (1)
bucket/aurora-rgb.json (1)
8-9: Please confirm the zip asset exists before merging.The v350 release upstream exposes an installer named
Aurora-setup-v350.exe, and I’m not seeing a siblingAurora-v350.zip. If that zip is missing, this manifest will 404 at install time—could you double-check the asset list and switch to the published installer (with the proper installer metadata) if the zip isn’t actually provided? (community.chocolatey.org)
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 @coderabbitai help to get the list of available commands and usage tips.
/verify
All changes look good.
Wait for review from human collaborators.
aurora-rgb
- [x] Lint
- [x] Description
- [x] License
- [x] Hashes
- [x] Checkver
- [x] Autoupdate