fluxdown: Add version 0.1.54

[zerx-lab]

Adds a manifest for FluxDown, a free, open-source (AGPL-3.0), Rust-powered multi-protocol download manager (IDM alternative). Supports HTTP/HTTPS/FTP/BitTorrent/HLS with intelligent segmentation and a browser extension.

• Homepage / repo: https://github.com/zerx-lab/FluxDown
• Portable install (x64 + arm64), installs flux_down.exe with a Start Menu shortcut
• checkver: "github"; autoupdate pulls hashes from the release SHA256SUMS.txt
• persist: settings.json (portable build stores settings next to the exe)

The pinned hash values were computed with SHA-256 directly from the published v0.1.54 portable zips.

Note: starting with the next release the upstream CI attaches SHA256SUMS.txt to each desktop release so the autoupdate.hash.url resolves; the v0.1.54 hashes above are pinned explicitly.

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request adds a new Scoop bucket manifest file, bucket/fluxdown.json, for FluxDown version 0.1.54. The manifest includes description, homepage, license, and notes fields, along with architecture-specific (64bit and arm64) portable download URLs and hashes. It also defines the binary name, shortcut entry, persisted settings file, checkver configuration, and autoupdate templates for both architectures.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested labels: package-request-needed

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is detailed, but it omits the required issue reference and the template checklist confirmations.	Add a Closes/Relates issue reference and include the template checkboxes, including the Contributing Guide confirmation.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title is concise, specific, and accurately summarizes adding FluxDown v0.1.54.
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.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

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 `@bucket/fluxdown.json`:
- Around line 2-10: The new FluxDown manifest is missing the required linked
package-request issue in the PR body/description. Update the request text to
reference the GitHub issue so it is traceable, and make sure the request
explicitly states it meets the package-request criteria for a widely used app,
stable release, and English documentation. Use the FluxDown manifest entry as
the target for the linked issue 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 2e496d9e-1dcb-4e0d-8432-bd85eea81fcc

📥 Commits

Reviewing files that changed from the base of the PR and between 17f3bd7 and 9c7eb93.

📒 Files selected for processing (1)

• bucket/fluxdown.json

[coderabbitai]

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Link the package-request issue.

This is a new manifest, but the PR body/description doesn’t include the required issue reference yet. Please add one so the request is traceable and meets the bucket policy, and confirm it satisfies the package-request acceptance criteria (widely used, stable release, English docs). As per path instructions, new package requests must include a linked GitHub issue in the description or PR body. See the contribution guide: https://github.com/ScoopInstaller/.github/blob/main/.github/CONTRIBUTING.md.

🤖 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/fluxdown.json` around lines 2 - 10, The new FluxDown manifest is
missing the required linked package-request issue in the PR body/description.
Update the request text to reference the GitHub issue so it is traceable, and
make sure the request explicitly states it meets the package-request criteria
for a widely used app, stable release, and English documentation. Use the
FluxDown manifest entry as the target for the linked issue reference.

Source: Path instructions

[ExLei]

/verify

[github-actions]

Your changes did not pass all checks.

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

fluxdown

• Lint
• Description
• License
• Hashes
• Checkver
• Autoupdate
• Autoupdate Hash Extraction

Check the full log for details.

[ExLei]

@zerx-lab 大佬，您或许可以参考下我这个Manifest #18216

[zerx-lab]

Closing this — I see #18216 already covered FluxDown and was declined because the project doesn't yet meet the Extras criteria (100+ stars / 50+ forks). FluxDown is currently at ~96 stars, so it's just under the bar. Withdrawing to avoid a duplicate request against an already-reviewed decision. In the meantime FluxDown is installable from its self-hosted bucket, and I'll revisit Extras once the criteria are met. Thanks for the review!