Update Fleet-maintained apps

[fleet-release]

Automated ingestion of latest Fleet-maintained app data.

Summary by CodeRabbit

• Chores
  • Updated DBeaver Community macOS version metadata to 26.0.3, including installer URL and validation checksums
  • Updated Stats macOS version metadata to 2.12.11, including installer URL and validation checksums

[claude]

Claude Code Review

This repository is configured for manual code reviews. Comment @claude review to trigger a review and subscribe this PR to future pushes, or @claude review once for a one-time review.

_{Tip: disable this comment in your organization's Code Review settings.}

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: a2c61a7b-e6f6-43eb-b22e-3d62e9adacb5

📥 Commits

Reviewing files that changed from the base of the PR and between ca1ab21 and 1d2947f.

📒 Files selected for processing (2)

• ee/maintained-apps/outputs/dbeaver-community/darwin.json
• ee/maintained-apps/outputs/stats/darwin.json

---

Walkthrough

This pull request updates version metadata for two maintained applications in Fleet. The DBeaver Community macOS entry is bumped from version 26.0.2 to 26.0.3, with corresponding updates to the version comparison query, installer URL, and SHA256 checksum. Similarly, the Stats macOS entry is updated from version 2.12.9 to 2.12.11 with the same set of field modifications. Both updates maintain the existing JSON structure and control flow without introducing new fields or altering app bundle identifiers.

Possibly related PRs

• Update Fleet-maintained apps #43744: Updates Fleet-maintained-app JSON metadata entries with the same pattern of version bumps and corresponding installer URL and checksum changes.
• Update Fleet-maintained apps #43444: Modifies the same ee/maintained-apps/outputs/stats/darwin.json file fields (version, patched query threshold, installer URL, and SHA256).

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The PR description is minimal but adequate for an automated process. However, it lacks required checklist items and properly formatted sections from the template.	Add relevant checklist items from the template (e.g., 'Changes file added', testing confirmation) or explicitly document why they don't apply to this automated data ingestion.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Update Fleet-maintained apps' directly aligns with the changeset, which updates version metadata for two Fleet-maintained applications (DBeaver Community and Stats).
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
• Commit unit tests in branch fma-2604192114

---

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