fontbase: Update to version 2.24.9, fix checkver

[soleige]

fontbase: Update to 2.24.9

Fixed the 404 download error by updating the version to 2.24.9.
Updated 'checkver' URL to use 'latest.yml' to fix future updates.

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

Summary by CodeRabbit

• Chores
  • Updated FontBase to version 2.24.9.
  • Replaced 64-bit installer link and updated its hash for secure verification.
  • Improved auto-update detection by switching to the latest.yml-based version retrieval.

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

[coderabbitai]

Walkthrough

Updates the FontBase package manifest to version 2.24.9, replacing the 64-bit download URL and SHA512 hash, and switching the version check from the previous fontba.se updates page to the releases.fontba.se/win/latest.yml endpoint with an updated regex for extracting the version.

Changes

Cohort / File(s)	Summary
FontBase package manifest update bucket/fontbase.json	Bumped version to 2.24.9; updated 64-bit executable download URL to FontBase-2.24.9.exe#/dl.7z; replaced 64-bit SHA512 hash with the new value; changed checkver from fontba.se/updates with regex ([\d.]+)</a" to releases.fontba.se/win/latest.yml with regex (?m)^version:\s*([0-9]+(?:\.[0-9]+)*)\s*$; retained autoupdate structure aligned to latest.yml-based retrieval.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Verify the provided SHA512 hash matches the FontBase-2.24.9.exe download.
• Confirm https://releases.fontba.se/win/latest.yml is reachable and contains a version: line matching the regex.
• Validate that autoupdate logic still functions with the new checkver endpoint and regex.

Suggested labels

review-needed

Suggested reviewers

• z-Fng

Poem

🐰 I hopped through bytes to find a sign,

FontBase trimmed and versioned fine,
2.24.9 in neat array,
latest.yml now leads the way,
Fonts leap high — a rabbit's rhyme! 🎨✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description check	✅ Passed	The description includes the required conventional PR title format and confirms reading the Contributing Guide, matching the template requirements. It also provides context about fixing the 404 error and checkver URL update.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check	✅ Passed	The title clearly summarizes the main changes: updating FontBase to version 2.24.9 and fixing the checkver mechanism, which directly align with the changeset modifications.

✨ 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]

Your changes did not pass all checks.

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

fontbase

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

Check the full log for details.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ca0bb3f and f1a9f70.

📒 Files selected for processing (1)

• bucket/fontbase.json (3 hunks)

🧰 Additional context used

🧠 Learnings (4)

📓 Common learnings

Learnt from: Gitoffthelawn
Repo: ScoopInstaller/Extras PR: 16106
File: bucket/czkawka-gui.json:25-25
Timestamp: 2025-09-05T09:41:52.653Z
Learning: For czkawka-gui manifests in Scoop Extras, the correct upstream filename pattern for Windows GUI builds in recent versions uses "gtk46" (without underscore), not "gtk_46" (with underscore). The autoupdate URL should use "windows_czkawka_gui_gtk46.zip" format. This was confirmed by a working 10.0.0 update with valid hash.

📚 Learning: 2025-09-22T21:07:08.991Z

Learnt from: SiriosDev
Repo: ScoopInstaller/Extras PR: 16204
File: bucket/ultravnc.json:13-13
Timestamp: 2025-09-22T21:07:08.991Z
Learning: The UltraVNC 1.6.4.0 archive uses "x64" and "x86" directory names for the architecture-specific folders, not "32" and "64" as might be expected from other software packages.

Applied to files:

• bucket/fontbase.json

📚 Learning: 2025-10-16T15:59:21.258Z

Learnt from: o-l-a-v
Repo: ScoopInstaller/Extras PR: 16349
File: bucket/fvim.json:45-49
Timestamp: 2025-10-16T15:59:21.258Z
Learning: In Scoop manifests, the `autoupdate.url` and `autoupdate.architecture.<arch>.url` fields must be valid URIs according to the JSON schema (defined with `"format": "uri"`). Variables like `$matchUrlx64` that contain only path segments must be combined with a base URL (e.g., `https://github.com/.../releases/download/`) to form a complete valid URI.

Applied to files:

• bucket/fontbase.json

📚 Learning: 2025-09-05T09:41:52.653Z

Learnt from: Gitoffthelawn
Repo: ScoopInstaller/Extras PR: 16106
File: bucket/czkawka-gui.json:25-25
Timestamp: 2025-09-05T09:41:52.653Z
Learning: For czkawka-gui manifests in Scoop Extras, the correct upstream filename pattern for Windows GUI builds in recent versions uses "gtk46" (without underscore), not "gtk_46" (with underscore). The autoupdate URL should use "windows_czkawka_gui_gtk46.zip" format. This was confirmed by a working 10.0.0 update with valid hash.

Applied to files:

• bucket/fontbase.json

🪛 GitHub Actions: Pull Requests

bucket/fontbase.json

[error] 1-1: Process completed with exit code 1. Fontbase manifest checks finished with errors in CI workflow.

🔇 Additional comments (2)

bucket/fontbase.json (2)

11-16: The autoupdate.hash.regex is correct as-is; the suggested change would break it.

Latest.yml provides sha512 in base64 format (m9QboUYAWDTN1wpKo5Ne1mNJlTXhWZPBzj0HIa9DQOv2iwOb0edqDezablrKK/8wCXmYlZi619ZjS3iEb40Zpg==), so the current "regex": "sha512:\\s+$base64" is correct. The manifest stores the hash in hex format, but autoupdate extracts from latest.yml which uses base64 encoding—both represent the same hash value in different encodings. The suggested regex using [A-Fa-f0-9]{128} would not match the actual base64 content and would cause autoupdate to fail.

The pre_install script with $PLUGINSDIR\\app-64.7z is standard Scoop pattern for 7z extraction from installers.

---

33-36: No action needed — $base64 is a valid Scoop autoupdate hash placeholder.

Scoop supports $base64 along with other built-in hash variables ($sha512, $sha256, $sha1, $md5, $checksum) in autoupdate.hash.regex blocks. The usage in your manifest is correct.

[soleige]

/verify

[github-actions]

All changes look good.

Wait for review from human collaborators.

fontbase

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

Check the full log for details.

[z-Fng]

Thanks for your contribution!