winbox-v3: Add version 3.43

[AkariiinMKII]

Closes #2731

• 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 support for MikroTik Winbox v3.43 for 32‑bit and 64‑bit systems.
  • Built-in automatic version detection and update handling.
  • Added start menu shortcuts for easier access.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

---

Walkthrough

Adds a new Scoop manifest bucket/winbox-v3.json for MikroTik RouterOS Winbox v3.43, declaring 64-bit and 32-bit download URLs, SHA-256 hashes, binary mappings, start menu shortcuts, and checkver/autoupdate entries that parse the MikroTik download page. (29 words)

Changes

Cohort / File(s)	Summary
Winbox v3 Package Manifest bucket/winbox-v3.json	New Scoop manifest for Winbox v3.43: adds x64 and x86 download URLs, SHA-256 hashes, bin/shortcuts mappings, and checkver/autoupdate configuration pointing to the MikroTik download page.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Poem

🐰 I found a manifest, shiny and new,
I hopped to the bucket and pushed it through.
Two archs and checksums, tidy and bright,
Winbox v3 now ready to light the night. ✨

🚥 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 winbox-v3 version 3.43, directly matching the changeset of adding the manifest file.
Description check	✅ Passed	The description includes the required conventional PR title format and confirmation of reading the Contributing Guide, but lacks specific details about the changes made.
Linked Issues check	✅ Passed	The PR successfully adds a winbox-v3 manifest with appropriate configuration for RouterOS Winbox v3, meeting all coding requirements from issue #2731.
Out of Scope Changes check	✅ Passed	All changes are within scope—only the new winbox-v3.json manifest file is added as required by the linked issue #2731.
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.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

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

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

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]

Your changes did not pass all checks.

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

winbox-v3

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

Check the full log for details.

[coderabbitai]

Actionable comments posted: 2

🤖 Fix all issues with AI agents

In `@bucket/winbox-v3.json`:
- Line 26: The 32-bit package currently exposes the executable as "winbox.exe"
in the "bin" field causing inconsistent CLI name vs the 64-bit config which
aliases "winbox64.exe" → "winbox"; update the 32-bit entry so the "bin" value
uses the canonical name "winbox" (or add an alias mapping from "winbox" to
"winbox.exe") so users can invoke "winbox" on both architectures—modify the
"bin" field that currently reads "winbox.exe" in the winbox-v3.json snippet to
the canonical "winbox" (or add an explicit alias mapping) to ensure parity with
the 64-bit config.
- Around line 35-38: The current checkver entry ("checkver" with regex "WinBox
([\\d.]+)<") targets a Livewire-rendered page so the regex will never match;
change the checkver to use a static/versioned source (for example a GitHub
releases RSS/JSON, an official API endpoint, or a direct file listing page)
instead of https://mikrotik.com/download, and update the "url" and matching
strategy accordingly (e.g., switch to a JSON/regexp on the releases feed or
point to a static HTML page that contains the version string). Locate the
"checkver" object in winbox-v3.json and replace the dynamic-page URL and regex
with the alternative source and an appropriate extractor (or use the
provider-specific releases endpoint) so the manifest can reliably extract the
WinBox version.

[AkariiinMKII]

/verify

[github-actions]

All changes look good.

Wait for review from human collaborators.

winbox-v3

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

Check the full log for details.

[AkariiinMKII]

/verify

[github-actions]

All changes look good.

Wait for review from human collaborators.

winbox-v3

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

Check the full log for details.