bitmessage: Deprecate manifest

[haussmann]

I believe bitmessage should be deprecated, because:

• The last release 0.6.3.2 was in February 2018
• The 64-bit version was dropped "there won't be a 64bit Windows binary for 0.6.3.2 due to a lack of time", even though this is a critical security release "Version 0.6.2 has a bug that can be exploited for remote code execution. This is an emergency release [...]" (source)
• Autoupdate for 64 bit is not working
• Based on an unmaintained Python 2 version (source)

Relates to #16379

• Use conventional PR title
• I have read the Contributing Guide

Summary by CodeRabbit

• Chores
  • Marked Bitmessage as deprecated. The messaging application is no longer actively maintained, with the last official release dating back to 2018.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

A deprecation notice metadata property was added to the Bitmessage JSON manifest file, documenting that the project is no longer actively maintained since its last release in 2018.

Changes

Cohort / File(s)	Change Summary
Deprecation Metadata deprecated/bitmessage.json	Added top-level ## property containing a deprecation notice indicating Bitmessage is no longer actively maintained (last release 2018)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A notice so simple, a tag now so clear,
Bitmessage rests, no longer here,
We mark deprecated things with care,
So others know what's no longer fair! 📝

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'bitmessage: Deprecate manifest' clearly and concisely summarizes the main change—deprecating the Bitmessage manifest based on the project's lack of maintenance.
Description check	✅ Passed	The description includes a clear rationale for deprecation, references supporting evidence, relates to issue #16379, and confirms completion of checklist items as required by the template.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7e7295f and 15e46d1.

📒 Files selected for processing (1)

• deprecated/bitmessage.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: WindowsPowerShell

🔇 Additional comments (2)

deprecated/bitmessage.json (2)

1-39: Deprecation content and formatting looks appropriate.

The deprecation message is clear, includes a date and reason aligned with the PR objectives (unmaintained project, last release in 2018). The JSON structure is syntactically valid and the rest of the manifest remains unchanged.

---

2-4: No issues found—the deprecation notice convention is correct.

The ## property is the official Scoop convention for comments in manifest files. The implementation in deprecated/bitmessage.json properly uses this standard by including an array with the deprecation message and date (2025-12-18), which is consistent with how Scoop manifests document metadata.

---

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