Skip to content

picocrypt-ng: Add version 2.09#17903

Open
scillidan wants to merge 1 commit into
ScoopInstaller:masterfrom
scillidan:picocrypt-ng
Open

picocrypt-ng: Add version 2.09#17903
scillidan wants to merge 1 commit into
ScoopInstaller:masterfrom
scillidan:picocrypt-ng

Conversation

@scillidan

Copy link
Copy Markdown
Contributor

Closes #17170

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

@coderabbitai

coderabbitai Bot commented May 27, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

This PR adds a new package manifest file for Picocrypt-NG v2.09 to the ScoopInstaller/Extras bucket. The manifest includes version metadata, project description and homepage, GPL-3.0-or-later license, the 64-bit portable executable download URL with SHA-256 hash verification, shortcut configuration with "Picocrypt NG" label, and autoupdate settings using version-templated release URLs for automatic updates.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and specifically describes the main change: adding version 2.09 of Picocrypt-NG to the manifest.
Description check ✅ Passed The PR description follows the template with required elements: it references the closed issue (#17170), confirms conventional PR title usage, and indicates the contributing guide was read.
Linked Issues check ✅ Passed The PR successfully implements all coding requirements from issue #17170: adds Picocrypt-NG with correct version (2.09), homepage URL, GPL-3.0-or-later license, download URL, SHA-256 hash, and autoupdate configuration.
Out of Scope Changes check ✅ Passed All changes are directly within scope: only the picocrypt-ng.json manifest file was modified to add version 2.09 with required metadata, with no extraneous changes.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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


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.

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

🧹 Nitpick comments (1)
bucket/picocrypt-ng.json (1)

1-26: Run local manifest validation before merge.

Please verify with:

scoop config debug true
scoop config gh_token <your-github-token>   # read-only token
.\bin\checkver.ps1 -App picocrypt-ng -f
.\bin\formatjson.ps1 -App picocrypt-ng
scoop install bucket\picocrypt-ng.json -a 64bit

If any checklist ambiguity comes up, use:

As per coding guidelines: “Provide clear instructions for testing the manifest locally before submission” and include contribution/wiki links for guidance.

🤖 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 `@bucket/picocrypt-ng.json` around lines 1 - 26, Add clear local validation and
testing steps for the picocrypt-ng manifest (picocrypt-ng.json) to your PR
description or a CONTRIBUTING note: list the exact commands to run (enable
debug, set GH token, run .\bin\checkver.ps1 -App picocrypt-ng -f,
.\bin\formatjson.ps1 -App picocrypt-ng, and scoop install
bucket\picocrypt-ng.json -a 64bit), and include links to the Scoop contribution
and manifest wiki pages for guidance (ScoopInstaller/.github CONTRIBUTING.md and
Scoop Wiki App-Manifests). This ensures reviewers can reproduce manifest
validation before merge; update the PR text (not the JSON fields) to contain
those commands and links.
🤖 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.

Nitpick comments:
In `@bucket/picocrypt-ng.json`:
- Around line 1-26: Add clear local validation and testing steps for the
picocrypt-ng manifest (picocrypt-ng.json) to your PR description or a
CONTRIBUTING note: list the exact commands to run (enable debug, set GH token,
run .\bin\checkver.ps1 -App picocrypt-ng -f, .\bin\formatjson.ps1 -App
picocrypt-ng, and scoop install bucket\picocrypt-ng.json -a 64bit), and include
links to the Scoop contribution and manifest wiki pages for guidance
(ScoopInstaller/.github CONTRIBUTING.md and Scoop Wiki App-Manifests). This
ensures reviewers can reproduce manifest validation before merge; update the PR
text (not the JSON fields) to contain those commands and links.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 5fb45b8f-80dc-4756-b85d-457046413412

📥 Commits

Reviewing files that changed from the base of the PR and between ec31d16 and 7487bf6.

📒 Files selected for processing (1)
  • bucket/picocrypt-ng.json

@scillidan

Copy link
Copy Markdown
Contributor Author

/verify

@github-actions

Copy link
Copy Markdown
Contributor

All changes look good.

Wait for review from human collaborators.

picocrypt-ng

  • Lint
  • Description
  • License
  • Hashes
  • Checkver
  • Autoupdate

Check the full log for details.

arvdk added a commit to arvdk/Extras that referenced this pull request Jun 9, 2026
@aliesbelik

Copy link
Copy Markdown
Collaborator

/verify

@github-actions

Copy link
Copy Markdown
Contributor

Your changes did not pass all checks.

Please address the issues in the manifest and comment starting with /verify to rerun the checks.

picocrypt-ng

  • Lint
  • Description
  • License
  • Hashes
  • Checkver
  • Autoupdate

Check the full log for details.

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.

[Request]: Picocrypt-NG

2 participants