Update Fleet-maintained apps - #50316
Conversation
Generated automatically with cmd/maintained-apps.
WalkthroughUpdated 13 maintained-app manifests. The changes set newer application versions, patch-query thresholds, installer URLs, and SHA-256 checksums for Windows and Darwin packages. Existing installation and uninstallation script references remain unchanged where noted. Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 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 `@ee/maintained-apps/outputs/raycast/darwin.json`:
- Around line 4-12: Update the Raycast Darwin manifest’s installer_url so
deployments to Intel Macs are supported, using a universal installer or an
architecture-aware URL rather than the current arm-only build. Keep the version,
checksums, script references, and query definitions unchanged.
🪄 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 Plus
Run ID: a84887d9-a2fd-464a-be98-a1de423ecb78
📒 Files selected for processing (13)
ee/maintained-apps/outputs/dataflare/darwin.jsonee/maintained-apps/outputs/dataflare/windows.jsonee/maintained-apps/outputs/eclipse-temurin-jdk-8/windows.jsonee/maintained-apps/outputs/eclipse-temurin-jre-8/windows.jsonee/maintained-apps/outputs/firefox@nightly/darwin.jsonee/maintained-apps/outputs/krita/darwin.jsonee/maintained-apps/outputs/mockoon/darwin.jsonee/maintained-apps/outputs/pgadmin4/darwin.jsonee/maintained-apps/outputs/pgadmin4/windows.jsonee/maintained-apps/outputs/postman/darwin.jsonee/maintained-apps/outputs/raycast/darwin.jsonee/maintained-apps/outputs/setapp/darwin.jsonee/maintained-apps/outputs/typora/darwin.json
| "version": "1.104.24", | ||
| "queries": { | ||
| "exists": "SELECT 1 FROM apps WHERE bundle_identifier = 'com.raycast.macos';", | ||
| "patched": "SELECT 1 WHERE NOT EXISTS (SELECT 1 FROM apps WHERE bundle_identifier = 'com.raycast.macos' AND version_compare(bundle_short_version, '1.104.23') < 0);" | ||
| "patched": "SELECT 1 WHERE NOT EXISTS (SELECT 1 FROM apps WHERE bundle_identifier = 'com.raycast.macos' AND version_compare(bundle_short_version, '1.104.24') < 0);" | ||
| }, | ||
| "installer_url": "https://releases.raycast.com/releases/1.104.23/download?build=arm", | ||
| "installer_url": "https://releases.raycast.com/releases/1.104.24/download?build=arm", | ||
| "install_script_ref": "f52a81be", | ||
| "uninstall_script_ref": "cb893329", | ||
| "sha256": "fdaa2d6f2719998f0548e2f351299130c7f3c2c37fdafd3ca0d7b88ad798da81", | ||
| "sha256": "927f5b65849e0122a3db73588965fbe8e2115c24e89c06d40804f26213dd1a0a", |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "## candidate files"
git ls-files | rg '(^ee/maintained-apps/outputs/raycast/darwin\.json$|server/mdm/maintainedapps/sync\.go$|maintain|raycast|darwin)' | head -200
echo
echo "## darwin.json snippet"
if [ -f ee/maintained-apps/outputs/raycast/darwin.json ]; then
cat -n ee/maintained-apps/outputs/raycast/darwin.json | sed -n '1,80p'
fi
echo
echo "## sync.go relevant section"
if [ -f server/mdm/maintainedapps/sync.go ]; then
wc -l server/mdm/maintainedapps/sync.go
cat -n server/mdm/maintainedapps/sync.go | sed -n '150,285p'
fi
echo
echo "## search installer_url consumers/field definitions"
rg -n "installer_url|InstallerUrl|bundle_identifier|architecture|arch|darwin|maintainedapps|raycast" server ee -S --glob '!**/*.min.js' | head -300Repository: fleetdm/fleet
Length of output: 11520
🌐 Web query:
Raycast macOS installer releases 1.104.24 build=arm build=intel download
💡 Result:
As of July 31, 2026, there is no public release of Raycast for macOS version 1.104.24. Raycast manages its software releases through its official website and automatic updates [1][2]. While the Homebrew Cask repository lists versions for Raycast, the most recent version trackable in public configuration files is 1.104.22 [2], and official changelogs last documented version 1.104.0 (released December 16, 2025) [3][4]. For the most accurate and up-to-date installer: - Visit the official Raycast website at https://www.raycast.com to download the latest version directly [1]. - Raycast updates are typically delivered automatically via the built-in updater within the application [2]. - If you are using Homebrew, you can install the latest available version using: brew install --cask raycast [5]. Raycast does not publish direct, permanent download links for specific build numbers (e.g., 1.104.24) to the public, as these are managed through their CDN and version-check endpoints [2].
Citations:
- 1: https://www.raycast.com/
- 2: https://raw.githubusercontent.com/Homebrew/homebrew-cask/master/Casks/r/raycast.rb
- 3: https://www.raycast.com/changelog/macos
- 4: https://www.raycast.com/changelog/macos/1-104-0
- 5: https://formulae.brew.sh/cask/raycast
🌐 Web query:
Raycast macOS download build parameter arm intel universal DMG
💡 Result:
Raycast is distributed as a universal binary for macOS, which includes support for both Apple Silicon (ARM) and Intel (x86_64) architectures within a single package [1][2]. Users do not need to manually select or download separate architecture-specific DMG files; the official download automatically provides the universal version that runs natively on the user's processor [2]. From a technical and programmatic perspective, the Raycast update and distribution infrastructure allows for targeted downloads using a build parameter. Specifically: 1. Build Parameter: When interacting with the Raycast release API (e.g., for automated installs or package management like Homebrew), you can specify the architecture using the build query parameter in the download URL [3][4]. - For Apple Silicon: Use build=arm [5][6][4]. - For Intel: Use build=x86_64 (or intel) [3][5][4]. 2. Official Distribution: The primary download from the official Raycast website [7] simplifies this process for general users by delivering the universal binary, ensuring compatibility regardless of the Mac's hardware architecture [2]. The use of universal binaries allows the application to detect the machine's architecture at runtime and execute the corresponding native code, avoiding the need for Rosetta 2 translation and ensuring optimal performance on both ARM and Intel Macs [1][2].
Citations:
- 1: https://doesitarm.com/app/raycast
- 2: https://raycast-discount-code.com/blog/raycast-download
- 3: https://raw.githubusercontent.com/Homebrew/homebrew-cask/master/Casks/r/raycast.rb
- 4: https://github.com/NixOS/nixpkgs/blob/8c91a71d13451abc40eb9dae8910f972f979852f/pkgs/by-name/ra/raycast/package.nix
- 5: railwhale/nixpkgs@c6921ea
- 6: https://github.com/Homebrew/homebrew-cask/blob/master/Casks/r/raycast.rb
- 7: https://www.raycast.com/
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "## exact files"
git ls-files -- ee/maintained-apps/outputs/raycast/darwin.json server/mdm/maintainedapps/sync.go | sed -n '1,20p'
echo
echo "## darwin.json"
if [ -f ee/maintained-apps/outputs/raycast/darwin.json ]; then
cat -n ee/maintained-apps/outputs/raycast/darwin.json | sed -n '1,120p'
fi
echo
echo "## sync.go"
if [ -f server/mdm/maintainedapps/sync.go ]; then
wc -l server/mdm/maintainedapps/sync.go
cat -n server/mdm/maintainedapps/sync.go | sed -n '160,290p'
fi
echo
echo "## architecture-related fields and maintainers docs/articles"
rg -n "architecture|arch|mac_arm|mac_intel|universal|installer_url|installerUrls|download_url|os|x86|intel|arm64|apple|raycast" \
ee/maintained-apps README mdm server article articles \
-S --glob '!**/*.min.js' | sed -n '1,260p'Repository: fleetdm/fleet
Length of output: 45768
🌐 Web query:
"Fleet maintained apps" "mac_arm" "mac_intel" "installer_url" "darwin.json"
💡 Result:
In Fleet, Fleet-maintained apps (FMA) use manifest files, such as darwin.json, located in the ee/maintained-apps/outputs/ directory to define installation metadata for macOS hosts [1][2]. These manifest files contain critical information for deployment, including the installer_url, installer_sha256, and references to installation/uninstallation scripts [1][3]. Regarding macOS architecture support: 1. Architecture Handling: Historically, many Fleet-maintained apps for macOS were provided as Apple Silicon-only versions rather than universal binaries [2]. Because of this, Fleet has worked to improve support for distinguishing between Apple Silicon (arm64), Intel (x86_64), and Universal installers [4][5]. 2. Configuration: Fleet manifests are configured to provide specific download links. When an application has separate installers for different architectures, the darwin.json manifest must be structured to ensure that both Apple Silicon and Intel clients receive the appropriate, compatible version [6]. 3. Recent Developments: Fleet has been actively working on updates to allow for multiple installers per title, which enables users to select the correct architecture during the "Add software" process [4]. This involves UI updates to display supported architectures and modifications to the underlying manifest logic to support these distinct artifact references [4]. 4. Automation and Safety: To prevent issues when deploying Apple Silicon-only apps to Intel hardware, Fleet has explored implementation strategies—such as existence check policy queries—that prevent unintended auto-installation on incompatible devices [5]. Developers maintaining these apps generate the darwin.json outputs from input manifests (often based on Homebrew casks) using Fleet's internal ingesters [7][8]. When updating these apps, the process typically involves bumping the version, updating the installer_url to the correct platform-specific or universal link, and verifying the installer_sha256 checksum [3][9][10].
Citations:
- 1: Initial app manifest structure in GitHub #26080
- 2: https://fleetdm.com/guides/fleet-maintained-apps
- 3: Update Fleet-maintained apps #49460
- 4: Software > Fleet-maintained apps: add an 'Arm,' 'x86' (for Intel), or 'Universal' for macOS and Windows installers #27503
- 5: Don't auto-install macOS Fleet-maintained apps on Intel Macs if the app is Apple Silicon only #27392
- 6: Update Fleet-maintained apps #49813
- 7: https://github.com/fleetdm/fleet/blob/main/ee/maintained-apps/README.md
- 8: Add Vivaldi as a Fleet-maintained app #41552
- 9: Update Fleet-maintained apps #49404
- 10: Update Fleet-maintained apps #49055
🌐 Web query:
"maintained apps" "darwin" "raycast" "Fleet" "installer_url"
💡 Result:
Fleet maintains a library of pre-configured applications, including Raycast, to simplify installation on macOS and Windows without requiring manual uploads or extra configuration [1]. These apps are defined by metadata manifest files located within the Fleet codebase, specifically in the directory ee/maintained-apps/outputs/. For Raycast on macOS, the relevant configuration is found in the ee/maintained-apps/outputs/raycast/darwin.json file [2][3][4]. This manifest file typically includes critical data for automated deployment, such as: - installer_url: The direct download link for the application installer [5][6][7]. - sha256: The checksum used for verification [2][5][6]. - Versioning information and SQL queries (e.g., for version_compare()) to detect installed versions and determine if an update is required [5][6][8][7]. Fleet automatically updates these manifests as new software versions are released, refreshing the installer_url, checksums, and versioning data to ensure hosts remain up-to-date [3][1][7]. You can manage these maintained apps directly through the Fleet software catalog interface or via GitOps configurations [1].
Citations:
- 1: https://fleetdm.com/guides/fleet-maintained-apps
- 2: Update Fleet-maintained apps #49330
- 3: f933652
- 4: Update Fleet-maintained apps #45503
- 5: Update Fleet-maintained apps #47962
- 6: Update Fleet-maintained apps #48540
- 7: Update Fleet-maintained apps #49857
- 8: https://fleetdm.com/software-catalog/raycast-darwin
Verify the Raycast manifest covers Intel hosts.
installer_url points at build=arm, and server/mdm/maintainedapps/sync.go copies the selected installer_url into the Darwin app record without architecture selection. If this entry deploys to Intel Macs, use a universal or architecture-aware installer URL.
🤖 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 `@ee/maintained-apps/outputs/raycast/darwin.json` around lines 4 - 12, Update
the Raycast Darwin manifest’s installer_url so deployments to Intel Macs are
supported, using a universal installer or an architecture-aware URL rather than
the current arm-only build. Keep the version, checksums, script references, and
query definitions unchanged.
Source: MCP tools
|
Closing in favor of #50347. |
2 participants
Automated ingestion of latest Fleet-maintained app data.
Summary by CodeRabbit