hongdown: Add version 0.4.3

[dahlia]

Closes #18005.

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

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR adds a new package manifest file bucket/hongdown.json to the Scoop Extras bucket. The manifest defines Hongdown Markdown formatter version 0.4.3, specifying the Windows executable name, release metadata (homepage and license URLs), architecture-specific download URLs for both 64-bit and ARM64 systems with corresponding SHA256 integrity hashes, and an autoupdate mechanism with version placeholders for automated updates.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Suggested labels

package-request-needed

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The PR title 'hongdown: Add version 0.4.3' clearly and specifically summarizes the main change—adding a new version of the hongdown manifest.
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.
Description check	✅ Passed	The PR description includes a reference to a related issue and confirms compliance with the repository's contribution guidelines and title format requirements.

_{✏️ 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

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

bucket/hongdown.json (1)

1-28: Run the standard local manifest checks before submission.

Use the required Scoop workflow for hongdown:

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

Reference docs:

• https://github.com/ScoopInstaller/.github/blob/main/.github/CONTRIBUTING.md
• https://github.com/ScoopInstaller/Scoop/wiki/App-Manifests

As per coding guidelines, provide clear instructions for checkver, formatjson, and per-architecture install testing for new manifests.

🤖 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/hongdown.json` around lines 1 - 28, Run the standard local manifest
checks for hongdown.json: enable debug and (optionally) set GH token, then run
.\bin\checkver.ps1 -App hongdown -f to validate the "checkver" field and release
detection, run .\bin\formatjson.ps1 -App hongdown to enforce manifest formatting
(verifying "version", "architecture", "autoupdate" and "bin" fields), and
perform per-architecture installs using scoop install bucket/hongdown.json -a
64bit and -a arm64 to validate the provided URLs/hashes in the "architecture"
block; if any step fails, update hongdown.json (fields: "version",
"architecture.*.url", "architecture.*.hash", "autoupdate") to correct the values
and re-run the checks.

Source: Coding guidelines

🤖 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/hongdown.json`:
- Around line 1-28: This new manifest (hongdown.json) lacks a linked
package-request issue; please create a package-request using the provided
template URL and then add the issue link to the manifest's "description" field
or the PR body and confirm the acceptance criteria (well-known usage, stable
release, English interface/docs). Use the package-request template URL from the
review, paste the created issue URL into the description value of hongdown.json
(or top of the PR body), and include a short note stating the manifest meets the
three checks so reviewers can verify.

---

Nitpick comments:
In `@bucket/hongdown.json`:
- Around line 1-28: Run the standard local manifest checks for hongdown.json:
enable debug and (optionally) set GH token, then run .\bin\checkver.ps1 -App
hongdown -f to validate the "checkver" field and release detection, run
.\bin\formatjson.ps1 -App hongdown to enforce manifest formatting (verifying
"version", "architecture", "autoupdate" and "bin" fields), and perform
per-architecture installs using scoop install bucket/hongdown.json -a 64bit and
-a arm64 to validate the provided URLs/hashes in the "architecture" block; if
any step fails, update hongdown.json (fields: "version", "architecture.*.url",
"architecture.*.hash", "autoupdate") to correct the values and re-run the
checks.

🪄 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: adc9f2e9-9f99-40fb-9e0b-f8de203c09f2

📥 Commits

Reviewing files that changed from the base of the PR and between 045cb9e and 29c0f19.

📒 Files selected for processing (1)

• bucket/hongdown.json

[aliesbelik]

/verify

[github-actions]

All changes look good.

Wait for review from human collaborators.

hongdown

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

Check the full log for details.