[email protected]: Remove checkver

[o-l-a-v]

Changes:

• Removed checkver and autoupdate

Because:

• Deprecated since 2025-09-26 ( https://github.com/facebook/flipper )
• No Windows artifact added to new releases since v0.239.0 released 2023-11-30

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

Summary by CodeRabbit

• Documentation

  • Added a top-level deprecation notice for the Windows artifact.

• Chores

  • Removed the automatic version-checking/update metadata that pointed to the previous repository.

[coderabbitai]

Walkthrough

Added a top-level ## deprecation notice to bucket/fbflipper.json and removed its checkver block that referenced the GitHub repository; no other manifest update logic was changed.

Changes

Cohort / File(s)	Summary
Manifest edits bucket/fbflipper.json	Inserted a top-level ## field containing a deprecation notice; removed the checkver block that referenced github: "https://github.com/facebook/flipper". No other autoupdate/version logic was changed.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• [email protected]: Remove checkver & autoupdate, add arm64 support, fix suggest #16427 — Similar manifest edits: removed checkver and added a top-level deprecation/metadata field.
• [email protected]: Checkver exclude versions with no build artifacts #16394 — Modifies checkver declaration and adds a top-level ## note in a bucket manifest.
• debugviewpp: Update to version 1.9.0.28, drop 32bit support, fix checkver & autoupdate #16375 — Edits the checkver block in another bucket manifest (related pattern of changes).

Poem

🐰 I nibble lines of JSON light,

A gentle note, a dusk in sight,
The checkver fades, the key says "done",
A quiet hop — the change is run. ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	The PR description is mostly complete and addresses the key requirements of the template. It includes a clear "Changes:" section explaining what was removed, a "Because:" section providing the reasoning with links and dates, and both required checkboxes are checked (conventional PR title format and confirmation of reading the Contributing Guide). While the description lacks an explicit issue reference in the format suggested by the template (e.g., "Relates to #16379"), this element is presented as guidance in HTML comments rather than as a strictly required section, making it a non-critical omission. The substantive content clearly communicates the intent and justification for the changes.
Title Check	✅ Passed	The pull request title "[email protected]: Remove checkver" is directly and specifically related to the main changes documented in the raw summary. The summary confirms that the checkver block containing the GitHub repository reference was removed from the fbflipper manifest, which is exactly what the title describes. The title is clear, concise, and non-misleading—it avoids vague terminology and accurately conveys the primary modification to the file. While the PR objectives also mention autoupdate removal, the raw_summary's documented changes focus on the checkver removal, which the title appropriately highlights.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• 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

• X
• Mastodon
• Reddit
• LinkedIn

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

[github-actions]

All changes look good.

Wait for review from human collaborators.

fbflipper

• Lint
• Description
• License
• Hashes

Check the full log for details.

[o-l-a-v]

Related: #16379.

[o-l-a-v]

Why keep autoupdate? Just curious.

[z-Fng]

IMO, if we keep the autoupdate field, users can still install a specific version via scoop install app@version. Otherwise:

PS> scoop install [email protected]
WARN  Given version (0.238.0) does not match manifest (0.239.0)
WARN  Attempting to generate manifest for 'fbflipper' (0.238.0)
'fbflipper' does not have autoupdate capability

P.S. If ScoopInstaller/Scoop#6370 gets merged, this will no longer be necessary and can be removed later.