Skip to content

Update Fleet-maintained apps - #48427

Merged
allenhouchins merged 2 commits into
mainfrom
fma-2606291657
Jun 29, 2026
Merged

Update Fleet-maintained apps#48427
allenhouchins merged 2 commits into
mainfrom
fma-2606291657

Conversation

@fleet-release

@fleet-release fleet-release commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

Automated ingestion of latest Fleet-maintained app data.

Summary by CodeRabbit

  • Bug Fixes
    • Updated app release metadata for multiple macOS and Windows apps so users get the latest available installers.
    • Bumped versions for Bezel, ClipBook, Cryptomator, Downie, DuckDuckGo, Genesys Cloud, MacWhisper, Miro, Nextcloud, Notepad.exe, Opera, Proton Drive, Reqable, WhatsApp, and Wins.

Generated automatically with cmd/maintained-apps.

@claude claude Bot left a comment

Copy link
Copy Markdown

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

coderabbitai Bot commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Walkthrough

Version metadata was updated for 16 maintained app output JSON files. Each change increments the version field, adjusts the queries.patched SQL version_compare threshold to match, updates the installer_url to the new release artifact, and replaces the sha256 checksum. Affected apps: Bezel (4.6.0), ClipBook (1.36.0), Cryptomator (1.19.3), Downie (4.12.9), DuckDuckGo (1.196.0), Genesys Cloud (2.51.916.0), MacWhisper (13.23.0), Miro (0.11.154), Nextcloud (33.0.7), Notepad.exe (1.4.1901), Opera (133.0), Proton Drive (3.0.2), Reqable macOS (3.2.0), Reqable Windows (3.2.1), WhatsApp (26.26.12), and Wins (3.4).

Possibly related PRs

  • fleetdm/fleet#48410: Updates the same ee/maintained-apps/outputs/reqable/windows.json entry with the same pattern of version, patched query, installer_url, and sha256 changes.
  • fleetdm/fleet#48387: Updates ee/maintained-apps/outputs/notepadexe/darwin.json with the same version-gate metadata bump pattern.
  • fleetdm/fleet#48357: Updates the same ee/maintained-apps/outputs/whatsapp/darwin.json entry by changing the queries.patched version cutoff and associated version metadata.
🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description is too vague and omits the required issue reference, checklist items, testing, and other template sections. Fill in the full template, including the related issue and the required checklist/testing/database sections, or remove sections that do not apply.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the main change: updating Fleet-maintained apps.
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.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fma-2606291657

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.

@coderabbitai coderabbitai Bot left a comment

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.

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/miro/windows.json`:
- Around line 9-12: The Miro Windows installer entry is pinned to a mutable
download URL, so the checksum can drift if the vendor republishes it. Update the
installer reference in the Miro windows.json entry to use an immutable,
versioned artifact or an internal mirror, and keep the existing sha256 tied to
that fixed asset so the install reproducibly matches the pinned hash.
🪄 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: dd39a154-db1a-4690-971b-cc78e58a5225

📥 Commits

Reviewing files that changed from the base of the PR and between 8e80e97 and 5528cd6.

📒 Files selected for processing (16)
  • ee/maintained-apps/outputs/bezel/darwin.json
  • ee/maintained-apps/outputs/clipbook/darwin.json
  • ee/maintained-apps/outputs/cryptomator/darwin.json
  • ee/maintained-apps/outputs/downie/darwin.json
  • ee/maintained-apps/outputs/duckduckgo/darwin.json
  • ee/maintained-apps/outputs/genesys-cloud/windows.json
  • ee/maintained-apps/outputs/macwhisper/darwin.json
  • ee/maintained-apps/outputs/miro/windows.json
  • ee/maintained-apps/outputs/nextcloud/windows.json
  • ee/maintained-apps/outputs/notepadexe/darwin.json
  • ee/maintained-apps/outputs/opera/darwin.json
  • ee/maintained-apps/outputs/proton-drive/windows.json
  • ee/maintained-apps/outputs/reqable/darwin.json
  • ee/maintained-apps/outputs/reqable/windows.json
  • ee/maintained-apps/outputs/whatsapp/darwin.json
  • ee/maintained-apps/outputs/wins/darwin.json

Comment on lines 9 to +12
"installer_url": "https://desktop.miro.com/platforms/win32-nsis-pu/Miro-setup.exe",
"install_script_ref": "c9d9747e",
"uninstall_script_ref": "66f6a4de",
"sha256": "24da9d6b31fd5429a773f1e30d7fb2b16ba789330201289f45920babf8fb0704",
"sha256": "0191332d9a1ed8e470552adbc752d71c7da0d21172223369ac18cb37ff9c89a1",

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.

🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

url='https://desktop.miro.com/platforms/win32-nsis-pu/Miro-setup.exe'
tmp="$(mktemp)"
trap 'rm -f "$tmp"' EXIT

echo "Effective URL:"
curl -fsSIL -o /dev/null -w '%{url_effective}\n' "$url"

echo
echo "Headers:"
curl -fsSIL "$url"

echo
echo "Downloading to compute current sha256..."
curl -fsSL --retry 3 --output "$tmp" "$url"
sha256sum "$tmp"

Repository: fleetdm/fleet

Length of output: 913


🌐 Web query:

Miro Windows installer URL versioned immutable desktop.miro.com platform win32 nsis pu Miro-setup.exe

💡 Result:

Miro does not utilize a public, versioned, or immutable URL structure for its Windows installer files [1][2]. Instead, Miro provides standardized download links via its official website, which consistently point to the latest available version [3][1]. For Windows, the primary installer is commonly referenced as Miro-setup.exe [4][5]. IT administrators and users typically access these installers through the official Miro apps page [3][1]. While older community documentation or legacy scripts may have referenced path structures like desktop.miro.com/platforms/..., Miro now directs users to their official download center for the most current MSI or EXE installers [3][1]. Key details regarding Miro Windows installation: - Official Source: All downloads should be sourced from the official Miro website (miro.com/apps/) to ensure security and validity [3][1][2]. - Installer Types: Miro offers various installers, including MSI versions for enterprise deployment (per-user and per-machine, with or without auto-updates) [1]. - Persistence/Immutability: There is no guarantee of immutability for these URLs; they are designed to serve the most recent release [1]. Automated deployment scripts that rely on static URLs often require maintenance as the underlying download infrastructure may change [6]. - Installation Framework: The Windows desktop application is built using technologies consistent with standard Windows installation frameworks (such as NSIS for older executables or MSI/MSIX for enterprise deployment) [1][7][8]. If you are automating deployment, it is recommended to use the official links provided in the Miro Help Center, which lists specific MSI installers for enterprise use, rather than attempting to construct URLs manually [1].

Citations:


Pin the installer to an immutable artifact. https://desktop.miro.com/platforms/win32-nsis-pu/Miro-setup.exe is a latest-style download URL, so the pinned sha256 can drift if Miro republishes the file; use a versioned asset or internal mirror instead.

🤖 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/miro/windows.json` around lines 9 - 12, The Miro
Windows installer entry is pinned to a mutable download URL, so the checksum can
drift if the vendor republishes it. Update the installer reference in the Miro
windows.json entry to use an immutable, versioned artifact or an internal
mirror, and keep the existing sha256 tied to that fixed asset so the install
reproducibly matches the pinned hash.

allenhouchins
allenhouchins previously approved these changes Jun 29, 2026
@allenhouchins
allenhouchins merged commit b547f1a into main Jun 29, 2026
12 of 13 checks passed
@allenhouchins
allenhouchins deleted the fma-2606291657 branch June 29, 2026 17:44
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.

2 participants