Update Fleet-maintained apps by fleet-release · Pull Request #44192 · fleetdm/fleet

fleet-release · 2026-04-25T21:18:12Z

Automated ingestion of latest Fleet-maintained app data.

Summary by CodeRabbit

Chores
- Updated version references, installer URLs, and checksums for multiple maintained applications: Claude, Cursor, Microsoft Edge, Spotify, Telegram, Warp, and Zed. These updates enable the system to reference the latest available releases for deployment and update management.

Generated automatically with cmd/maintained-apps.

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 · 2026-04-25T21:21:20Z

Walkthrough

This PR updates version numbers and associated metadata for eight maintained applications across the Fleet managed-apps catalog. For each application, the changes include: the version field, the patched SQL query's version-compare threshold, the installer download URL, and the corresponding SHA256 checksum. Updated applications include Claude, Cursor, Microsoft Edge, Spotify, Telegram, Warp, and Zed across their respective platform-specific manifest files.

Possibly related PRs

Update Fleet-maintained apps #43739: Updates the same maintained-app JSON entries (Claude, others) by bumping version, adjusting patched SQL checks, and replacing installer URLs and SHA256 checksums.
Update Fleet-maintained apps #43662: Modifies the same Fleet-maintained-app JSON files (Claude, Cursor manifests) by updating version strings, patched-query thresholds, installer URLs, and checksums.
Update Fleet-maintained apps #43523: Automated version-bump updates to the same maintained-app JSON manifests (Claude, Cursor, Warp, Spotify, Zed) with matching field changes to version, patched query, installer URL, and SHA256.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description 'Automated ingestion of latest Fleet-maintained app data' is very brief and generic, lacking concrete details about which apps were updated or why, making it difficult to understand the scope and context of changes.	Expand the description to specify which apps were updated (Claude, Cursor, Microsoft Edge, Spotify, Telegram, Warp, Zed), their new versions, and the purpose of the update (e.g., security patches, feature releases).

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Update Fleet-maintained apps' directly and clearly summarizes the main change—updating version data for multiple Fleet-maintained applications across different platforms.
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.

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

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

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

coderabbitai

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@ee/maintained-apps/outputs/warp/darwin.json`:
- Line 12: The JSON entry currently has the "sha256" field set to "no_check",
leaving the installer unverified; replace the "sha256": "no_check" value with
the actual SHA256 checksum for the Darwin installer by fetching the checksum
from Warp's official release metadata (or vendor's published checksums) and
update the field to that hex string; if automation is needed, add logic to your
ingestion pipeline to query Warp release metadata (or GitHub/official release
assets) and inject the checksum into the "sha256" key so future ingestions
populate a verified checksum instead of "no_check".

In `@ee/maintained-apps/outputs/zed/darwin.json`:
- Line 4: The "version" field currently set to "0.233.10" is invalid; update the
value of the JSON key "version" (the "version": "0.233.10" entry) to the valid
release string "0.233.9" so the darwin.json manifest references an existing Zed
release.

🪄 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: a9f5cb58-16ee-4fa8-b830-5e5682a448b4

📥 Commits

Reviewing files that changed from the base of the PR and between fc7af80 and e7f5044.

📒 Files selected for processing (9)

ee/maintained-apps/outputs/claude/darwin.json
ee/maintained-apps/outputs/claude/windows.json
ee/maintained-apps/outputs/cursor/darwin.json
ee/maintained-apps/outputs/cursor/windows.json
ee/maintained-apps/outputs/microsoft-edge/darwin.json
ee/maintained-apps/outputs/spotify/windows.json
ee/maintained-apps/outputs/telegram/windows.json
ee/maintained-apps/outputs/warp/darwin.json
ee/maintained-apps/outputs/zed/darwin.json

coderabbitai · 2026-04-25T21:21:23Z

+      "installer_url": "https://releases.warp.dev/stable/v0.2026.04.22.08.46.stable_02/Warp.dmg",
      "install_script_ref": "42b4bf58",
      "uninstall_script_ref": "54d05203",
      "sha256": "no_check",


⚠️ Potential issue | 🟠 Major

Consider adding SHA256 checksum validation for security.

The sha256 field is set to "no_check", which means the installer is downloaded and executed without cryptographic verification. This creates a security risk if the download source is compromised or subject to man-in-the-middle attacks.

While this appears to be intentional for the automated ingestion process, consider obtaining and including the actual SHA256 checksum from Warp's release metadata to ensure installer integrity.

Would you like me to help research whether Warp publishes SHA256 checksums for their releases that could be automated into this ingestion process?

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed. In `@ee/maintained-apps/outputs/warp/darwin.json` at line 12, The JSON entry currently has the "sha256" field set to "no_check", leaving the installer unverified; replace the "sha256": "no_check" value with the actual SHA256 checksum for the Darwin installer by fetching the checksum from Warp's official release metadata (or vendor's published checksums) and update the field to that hex string; if automation is needed, add logic to your ingestion pipeline to query Warp release metadata (or GitHub/official release assets) and inject the checksum into the "sha256" key so future ingestions populate a verified checksum instead of "no_check".

coderabbitai · 2026-04-25T21:21:23Z

  "versions": [
    {
-      "version": "0.233.5",
+      "version": "0.233.10",


⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🌐 Web query:

Zed editor version 0.233.10 release

💡 Result:

No evidence found for a Zed editor release version 0.233.10. The closest versions are 0.233.9 (released around 2026-04-24, fixing agent threads migration issue after parallel-agents sidebar upgrade) and earlier ones like 0.233.7 mentioned on the homepage. Zed releases weekly stable versions in April 2026, with features like parallel AI agents, but 0.233.10 is not documented on official sites (zed.dev/releases/stable, GitHub zed-industries/zed), download page (0.232.2 as of April 15), or recent articles.

Citations:

1: https://zed.dev/releases/stable

2: https://zed.dev/releases/stable/0.233.9

3: https://zed.dev/download

4: https://zed.dev/

5: https://github.com/zed-industries/zed/releases/tag/v0.231.2

6: https://github.com/zed-industries/zed/releases/latest

7: https://zed.dev/releases/stable/0.230.0

8: https://zed.dev/releases/stable/0.232.2

9: https://zed.dev/releases/stable/latest

Version 0.233.10 does not exist. Zed's latest available release is 0.233.9 (released around 2026-04-24). Update this to a valid version number.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed. In `@ee/maintained-apps/outputs/zed/darwin.json` at line 4, The "version" field currently set to "0.233.10" is invalid; update the value of the JSON key "version" (the "version": "0.233.10" entry) to the valid release string "0.233.9" so the darwin.json manifest references an existing Zed release.

Update Fleet-maintained apps.

e7f5044

Generated automatically with cmd/maintained-apps.

fleet-release requested a review from allenhouchins April 25, 2026 21:18

claude Bot reviewed Apr 25, 2026

View reviewed changes

fleet-release temporarily deployed to Docker Hub April 25, 2026 21:18 — with GitHub Actions Inactive

github-actions Bot mentioned this pull request Apr 25, 2026

Update Fleet-maintained apps #44187

Closed

coderabbitai Bot reviewed Apr 25, 2026

View reviewed changes

allenhouchins approved these changes Apr 26, 2026

View reviewed changes

allenhouchins merged commit 62cd295 into main Apr 26, 2026
8 checks passed

allenhouchins deleted the fma-2604252115 branch April 26, 2026 12:35

This was referenced Apr 28, 2026

Update Fleet-maintained apps #44271

Merged

Update Fleet-maintained apps #44384

Merged

Update Fleet-maintained apps #44655

Merged

coderabbitai Bot mentioned this pull request Jun 9, 2026

Update Fleet-maintained apps #47231

Closed

Navigation Menu

Uh oh!

Update Fleet-maintained apps - #44192

Update Fleet-maintained apps#44192
allenhouchins merged 1 commit into
mainfrom
fma-2604252115

fleet-release commented Apr 25, 2026 •

edited by coderabbitai Bot

Loading

Uh oh!

claude Bot left a comment

Uh oh!

coderabbitai Bot commented Apr 25, 2026

❌ Failed checks (1 inconclusive)

Uh oh!

coderabbitai Bot left a comment

Uh oh!

coderabbitai Bot Apr 25, 2026

Uh oh!

coderabbitai Bot Apr 25, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

fleet-release commented Apr 25, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary by CodeRabbit

Uh oh!

claude Bot left a comment

Choose a reason for hiding this comment

Claude Code Review

Uh oh!

coderabbitai Bot commented Apr 25, 2026

Walkthrough

Possibly related PRs

❌ Failed checks (1 inconclusive)

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

coderabbitai Bot Apr 25, 2026

Choose a reason for hiding this comment

Uh oh!

coderabbitai Bot Apr 25, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

fleet-release commented Apr 25, 2026 •

edited by coderabbitai Bot

Loading