Skip to content

Update Fleet-maintained apps#43822

Merged
allenhouchins merged 1 commit intomainfrom
fma-2604202121
Apr 21, 2026
Merged

Update Fleet-maintained apps#43822
allenhouchins merged 1 commit intomainfrom
fma-2604202121

Conversation

@fleet-release
Copy link
Copy Markdown
Contributor

@fleet-release fleet-release commented Apr 20, 2026

Automated ingestion of latest Fleet-maintained app data.

Summary by CodeRabbit

  • Chores
    • Updated application metadata to support newer versions of ChatGPT, Claude, Cursor, Discord, Docker Desktop, Loom, OrbStack, and Zed across macOS and Windows platforms.

Generated automatically with cmd/maintained-apps.
Copy link
Copy Markdown

@claude claude Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Apr 20, 2026

Walkthrough

This PR updates version metadata for nine maintained applications across multiple platforms. For each application entry in JSON configuration files (ChatGPT, Claude, Cursor, Discord, Docker Desktop, Loom, OrbStack, and Zed), the following fields are updated: version field to a newer release number, queries.patched SQL query threshold to match the new version, installer_url to point to the new version's installer artifact, and sha256 checksum to match the updated installer. No code logic or exported entities are modified.

Possibly related PRs

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Description check ❓ Inconclusive The description is minimal but accurately reflects the PR's automated nature. However, it lacks required checklist items from the template (changes files, testing, validation), which are typically expected for production changes. Clarify whether checklist items are intentionally omitted for automated updates, or add relevant completed/N/A checklist items to follow the repository's contribution guidelines.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title 'Update Fleet-maintained apps' directly summarizes the main change: updating version metadata and checksums across multiple maintained application configuration files.
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-2604202121

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.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 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/zed/darwin.json`:
- Line 9: Replace the indirect GitHub redirect URL in the "installer_url" field
with Zed's official programmatic endpoint using the pattern
https://cloud.zed.dev/releases/{channel}/{version}/download?asset=zed&os=macos&arch=aarch64
(e.g., for v0.232.3 use
https://cloud.zed.dev/releases/stable/0.232.3/download?asset=zed&os=macos&arch=aarch64),
and then re-download that asset to compute and update the SHA256 checksum value
in the same darwin.json to ensure it matches the actual file; locate the
"installer_url" key in the JSON and update both the URL and the checksum entry
accordingly.
🪄 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: c01bc8f8-c788-429d-8b3d-59f72d946456

📥 Commits

Reviewing files that changed from the base of the PR and between b2b8254 and c6e97e6.

📒 Files selected for processing (11)
  • ee/maintained-apps/outputs/chatgpt/darwin.json
  • 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/discord/darwin.json
  • ee/maintained-apps/outputs/discord/windows.json
  • ee/maintained-apps/outputs/docker-desktop/darwin.json
  • ee/maintained-apps/outputs/loom/darwin.json
  • ee/maintained-apps/outputs/orbstack/darwin.json
  • ee/maintained-apps/outputs/zed/darwin.json

"patched": "SELECT 1 WHERE NOT EXISTS (SELECT 1 FROM apps WHERE bundle_identifier = 'dev.zed.Zed' AND version_compare(bundle_short_version, '0.232.3') < 0);"
},
"installer_url": "https://zed.dev/api/releases/stable/0.232.2/Zed-aarch64.dmg",
"installer_url": "https://zed.dev/api/releases/stable/0.232.3/Zed-aarch64.dmg",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: Verify the Zed installer URL is accessible and the SHA256 checksum matches.

INSTALLER_URL="https://zed.dev/api/releases/stable/0.232.3/Zed-aarch64.dmg"
EXPECTED_SHA256="2f6ca2b175772e57c1d5b2893f8c8556e16581341f9568ee0ce4f84f5128b488"

# Check if URL is accessible
echo "Checking if installer URL is accessible..."
HTTP_STATUS=$(curl -o /dev/null -s -w "%{http_code}" -I "$INSTALLER_URL")
if [ "$HTTP_STATUS" -eq 200 ]; then
  echo "✓ URL is accessible (HTTP $HTTP_STATUS)"
else
  echo "✗ URL returned HTTP $HTTP_STATUS"
  exit 1
fi

# Download and verify checksum
echo "Downloading installer to verify SHA256..."
TEMP_FILE=$(mktemp)
curl -sL "$INSTALLER_URL" -o "$TEMP_FILE"

echo "Computing SHA256 checksum..."
if command -v sha256sum > /dev/null; then
  ACTUAL_SHA256=$(sha256sum "$TEMP_FILE" | awk '{print $1}')
elif command -v shasum > /dev/null; then
  ACTUAL_SHA256=$(shasum -a 256 "$TEMP_FILE" | awk '{print $1}')
else
  echo "✗ No SHA256 utility found"
  rm "$TEMP_FILE"
  exit 1
fi

echo "Expected: $EXPECTED_SHA256"
echo "Actual:   $ACTUAL_SHA256"

if [ "$ACTUAL_SHA256" = "$EXPECTED_SHA256" ]; then
  echo "✓ SHA256 checksum matches"
else
  echo "✗ SHA256 checksum mismatch"
  rm "$TEMP_FILE"
  exit 1
fi

rm "$TEMP_FILE"
echo "All checks passed!"

Repository: fleetdm/fleet

Length of output: 123


🏁 Script executed:

#!/bin/bash
# Follow the redirect to see where it points
INSTALLER_URL="https://zed.dev/api/releases/stable/0.232.3/Zed-aarch64.dmg"

echo "Checking redirect chain..."
curl -sI -L "$INSTALLER_URL" | head -20

echo ""
echo "Checking final URL after redirects..."
curl -s -w "%{redirect_url}\n" -o /dev/null "$INSTALLER_URL"

echo ""
echo "Checking if version 0.232.3 exists by testing base release API..."
curl -s "https://zed.dev/api/releases/stable" | head -c 500

Repository: fleetdm/fleet

Length of output: 1223


🌐 Web query:

Zed editor release API URL format aarch64 dmg

💡 Result:

The Zed editor provides a release API for downloading the aarch64 (ARM64) macOS DMG via https://cloud.zed.dev/releases/{channel}/{version}/download?asset=zed&os=macos&arch=aarch64&source=install.sh. - channel: stable (default), preview, etc. - version: specific version like 0.232.2, or 'latest'. For latest stable aarch64 macOS DMG: https://cloud.zed.dev/releases/stable/latest/download?asset=zed&os=macos&arch=aarch64&source=install.sh This downloads Zed-aarch64.dmg, as used in the official install.sh script. GitHub releases also host Zed-aarch64.dmg assets (e.g., https://github.com/zed-industries/zed/releases/download/v0.220.6/Zed-aarch64.dmg), accessible via GitHub API: https://api.github.com/repos/zed-industries/zed/releases/latest with assets[].browser_download_url where name="Zed-aarch64.dmg". The zed.dev API is the primary programmatic method shown in official sources.

Citations:


Use the official Zed release API endpoint format instead of the indirect redirect.

The current installer URL redirects to GitHub (HTTP 307 → https://github.com/zed-industries/zed/releases/download/v0.232.3/Zed-aarch64.dmg), but Zed's official documentation shows the primary programmatic endpoint is https://cloud.zed.dev/releases/{channel}/{version}/download?asset=zed&os=macos&arch=aarch64. Update the URL to use the official format:

https://cloud.zed.dev/releases/stable/0.232.3/download?asset=zed&os=macos&arch=aarch64

Also verify the SHA256 checksum against the actual downloaded file to ensure correctness.

🤖 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 9, Replace the indirect
GitHub redirect URL in the "installer_url" field with Zed's official
programmatic endpoint using the pattern
https://cloud.zed.dev/releases/{channel}/{version}/download?asset=zed&os=macos&arch=aarch64
(e.g., for v0.232.3 use
https://cloud.zed.dev/releases/stable/0.232.3/download?asset=zed&os=macos&arch=aarch64),
and then re-download that asset to compute and update the SHA256 checksum value
in the same darwin.json to ensure it matches the actual file; locate the
"installer_url" key in the JSON and update both the URL and the checksum entry
accordingly.

@allenhouchins allenhouchins merged commit 6d4e0b5 into main Apr 21, 2026
8 checks passed
@allenhouchins allenhouchins deleted the fma-2604202121 branch April 21, 2026 01:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants