Update Fleet-maintained apps - #43636
Conversation
Generated automatically with cmd/maintained-apps.
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
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.
GitHub Actions
Inactive
Review Summary by QodoUpdate Fleet-maintained apps to latest versions
WalkthroughsDescription• Update 12 Fleet-maintained app versions to latest releases • Refresh installer URLs and SHA256 checksums for updated versions • Update version comparison queries to match new app versions Diagramflowchart LR
A["Fleet-maintained Apps"] -- "Version Updates" --> B["12 Applications Updated"]
B -- "Cursor, Dialpad, GitKraken" --> C["macOS & Windows Versions"]
B -- "Chrome, Notion, OneDrive" --> D["Platform-specific Releases"]
C -- "Refresh URLs & Checksums" --> E["Updated JSON Configs"]
D -- "Refresh URLs & Checksums" --> E
File Changes1. ee/maintained-apps/outputs/cursor/darwin.json
|
Code Review by Qodo🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)
Great, no issues found!Qodo reviewed your code and found no material issues that require reviewⓘ The new review experience is currently in Beta. Learn more |
WalkthroughThis PR updates version metadata and installer information for 12 managed applications across 11 JSON manifest files in the maintained-apps directory. For each application (Cursor, Dialpad, GitKraken, Google Chrome, JetBrains Toolbox, Notion, OneDrive, Signal, Spotify, and Yubico Authenticator), the updates include the version number, the patched query threshold, the installer URL pointing to the new version artifact, and the SHA256 checksum matching the new installer binary. No script references, query logic, or JSON structure were modified. Possibly related PRs
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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.
🧹 Nitpick comments (1)
ee/maintained-apps/outputs/yubico-authenticator/windows.json (1)
4-4: Consider pre-merge verification of artifact reachability and SHA256 alignment.The metadata is internally consistent and the SHA256 format is valid. However, the artifact reachability and checksum should be validated against the live GitHub release before merging. Runtime validation in
cmd/maintained-apps/validate/windows.go(lines 191–200) will catch SHA256 mismatches when installations occur, but pre-merge verification is a best practice to avoid deploy-time failures.Line 9 (installer_url) and Line 12 (sha256) should be tested against the live artifact.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@ee/maintained-apps/outputs/yubico-authenticator/windows.json` at line 4, The JSON entry for version "7.3.3" has an installer_url and sha256 that need pre-merge verification: fetch the artifact at the installer_url, compute its SHA256 and confirm it exactly matches the sha256 field in the JSON; if it does not, update the sha256 value (or correct the installer_url if the wrong asset was referenced); also ensure the artifact is reachable (HTTP 200) and re-run the repository's SHA validation routine locally (the validation logic that checks installer SHA256 at runtime) to confirm the same result before merging.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@ee/maintained-apps/outputs/yubico-authenticator/windows.json`:
- Line 4: The JSON entry for version "7.3.3" has an installer_url and sha256
that need pre-merge verification: fetch the artifact at the installer_url,
compute its SHA256 and confirm it exactly matches the sha256 field in the JSON;
if it does not, update the sha256 value (or correct the installer_url if the
wrong asset was referenced); also ensure the artifact is reachable (HTTP 200)
and re-run the repository's SHA validation routine locally (the validation logic
that checks installer SHA256 at runtime) to confirm the same result before
merging.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 5e219459-2a0b-49eb-ad63-24eaafe105fe
📒 Files selected for processing (12)
ee/maintained-apps/outputs/cursor/darwin.jsonee/maintained-apps/outputs/cursor/windows.jsonee/maintained-apps/outputs/dialpad/darwin.jsonee/maintained-apps/outputs/gitkraken/darwin.jsonee/maintained-apps/outputs/google-chrome/windows.jsonee/maintained-apps/outputs/jetbrains-toolbox/darwin.jsonee/maintained-apps/outputs/notion/windows.jsonee/maintained-apps/outputs/onedrive/darwin.jsonee/maintained-apps/outputs/signal/darwin.jsonee/maintained-apps/outputs/spotify/darwin.jsonee/maintained-apps/outputs/yubico-authenticator/darwin.jsonee/maintained-apps/outputs/yubico-authenticator/windows.json
3 participants
Automated ingestion of latest Fleet-maintained app data.
Summary by CodeRabbit
Release Notes