Skip to content

Conversation

@IgorMundstein
Copy link
Contributor

@IgorMundstein IgorMundstein commented Sep 11, 2025

Adds the initial Scoop manifest for WinMemoryCleaner 3.0.2.

Portable RAM cleaner using native Windows features to optimize memory.

No related issue (new manifest)

  • Use conventional PR title: <manifest-name[@version]|chore>: <general summary of the pull request>
  • I have read the Contributing Guide

Summary by CodeRabbit

  • New Features
    • Added a Scoop manifest to enable installing WinMemoryCleaner (v3.0.2).
    • Creates a shortcut for easy access after installation.
    • Includes checksum verification for secure downloads.
    • Supports automatic version checking and streamlined updates.

@coderabbitai
Copy link

coderabbitai bot commented Sep 11, 2025

Walkthrough

Adds a new Scoop manifest for WinMemoryCleaner (version 3.0.2) including metadata, download URL with SHA256, install targets (bin and shortcut), GitHub-based version check, and an autoupdate template.

Changes

Cohort / File(s) Summary
Scoop Manifest Addition
bucket/winmemorycleaner.json
New Scoop manifest defining v3.0.2 with description, homepage, license, URL, SHA256, bin, shortcuts, checkver: github, and autoupdate URL template.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Pre-merge checks (2 passed, 1 warning)

❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Description Check ⚠️ Warning The description provides a short summary of the manifest and application and has the template checkboxes marked, but it omits a required related issue reference and does not include the template's "Closes #XXXX" or "Relates to #XXXX" line despite the repository's requirement to open a relevant Package Request or Bug Report before creating a new manifest PR; therefore the description does not fully conform to the template. Please open a related issue (Package Request) for this new manifest and update the PR description to include "Closes #XXXX" or "Relates to #XXXX", confirm you searched for similar issues/PRs, and optionally expand the description with installation/verification steps or rationale for maintainers.
✅ Passed checks (2 passed)
Check name Status Explanation
Title Check ✅ Passed The PR title "winmemorycleaner: Add version 3.0.2" follows the repository's conventional format, is concise, and clearly summarizes the main change (adding the WinMemoryCleaner v3.0.2 manifest), so it accurately reflects the changes in the changeset.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.

Poem

I nibbled through bytes in a tidy scene,
A shiny new manifest—quick and clean!
Version set, hash in line,
URLs ready, looking fine.
Hop, hop! Scoop now knows the glean—
WinMemoryCleaner, crisp and lean. 🐇✨

✨ Finishing touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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 and usage tips.

@github-actions
Copy link
Contributor

All changes look good.

Wait for review from human collaborators.

winmemorycleaner

  • Description
  • License
  • Hashes
  • Checkver
  • Autoupdate

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (1)
bucket/winmemorycleaner.json (1)

14-15: Optional: add a user note about admin rights.

Upstream states the app needs administrator privileges; a note can reduce confusion for Scoop users. (github.com)

   ],
-  "checkver": "github",
+  "notes": "WinMemoryCleaner requires administrator privileges to run and may prompt for UAC elevation.",
+  "checkver": "github",
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e54d282 and aa81d09.

📒 Files selected for processing (1)
  • bucket/winmemorycleaner.json (1 hunks)
🔇 Additional comments (4)
bucket/winmemorycleaner.json (4)

8-14: Keeping bin is appropriate (console mode supported).

The app supports command-line arguments; exposing the exe via bin is useful. Shortcut looks fine. (github.com)


15-18: checkver/autoupdate look good for GitHub tags.

This will track the latest stable tag and expand $version correctly.


2-7: Verify SHA256 for WinMemoryCleaner 3.0.2 release

Version and download URL in bucket/winmemorycleaner.json match upstream 3.0.2; the sandbox couldn't compute the release binary's SHA256 — confirm the "hash" field equals the SHA256 of the downloaded binary.

Location: bucket/winmemorycleaner.json (lines 2–7)

Windows (PowerShell):
Invoke-WebRequest 'https://github.com/IgorMundstein/WinMemoryCleaner/releases/download/3.0.2/WinMemoryCleaner.exe' -OutFile WinMemoryCleaner-3.0.2.exe; (Get-FileHash WinMemoryCleaner-3.0.2.exe -Algorithm SHA256).Hash

Linux/macOS:
curl -sL 'https://github.com/IgorMundstein/WinMemoryCleaner/releases/download/3.0.2/WinMemoryCleaner.exe' -o WinMemoryCleaner-3.0.2.exe && shasum -a 256 WinMemoryCleaner-3.0.2.exe | awk '{print $1}'


6-7: Do not mark this asset as 64‑bit — it is 32‑bit (PE32).

Downloaded binary reports PE header magic 0x10B (PE32) and SHA256 = 5dcaa33af0034ac8f40c8109d5c46858de4f8ed53b9989e7a8cb59ed7cb4dc6d (matches manifest). If you want architecture-scoped fields, use a "32bit" key and mirror autoupdate under that key. Applies to bucket/winmemorycleaner.json lines 6-7 and 15-18.

Likely an incorrect or invalid review comment.

"version": "3.0.2",
"description": "Portable RAM cleaner using native Windows features to optimize memory.",
"homepage": "https://github.com/IgorMundstein/WinMemoryCleaner",
"license": "GPL-3.0-only",
Copy link

Choose a reason for hiding this comment

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

💡 Verification agent

🧩 Analysis chain

Confirm SPDX license identifier accuracy (“-only” vs “-or-later”).

Repo indicates GPL-3.0, but whether it’s “only” or “or-later” depends on LICENSE text. Ensure this matches upstream. (github.com)

If it mentions “any later version,” switch to GPL-3.0-or-later.


🏁 Script executed:

#!/usr/bin/env bash
curl -fsSL https://raw.githubusercontent.com/IgorMundstein/WinMemoryCleaner/main/LICENSE | rg -n 'any later version|either version 3'

Length of output: 254


Update SPDX license identifier to GPL-3.0-or-later

LICENSE contains "either version 3 of the License, or (at your option) any later version" (LICENSE lines 639–640); change bucket/winmemorycleaner.json (line 5) from "GPL-3.0-only" to "GPL-3.0-or-later".

🤖 Prompt for AI Agents
In bucket/winmemorycleaner.json around line 5, the SPDX license identifier is
set to "GPL-3.0-only" but the project's LICENSE states "either version 3 of the
License, or (at your option) any later version"; update the identifier to
"GPL-3.0-or-later" to reflect the correct permissive version range and save the
JSON file.

@IgorMundstein IgorMundstein deleted the update/winmemorycleaner-3.0.2 branch September 11, 2025 17:19
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