Update Fleet-maintained apps#46697
Conversation
Generated automatically with cmd/maintained-apps.
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.
WalkthroughThis PR updates version metadata for two Google applications on Windows. Chrome Remote Desktop Host is bumped from version 148.0.7778.23 to 149.0.7827.18, including updates to the installer URL, sha256 checksum, and SQL patched-version comparison. Google Chrome is bumped from 148.0.7778.217 to 149.0.7827.54, with corresponding updates to the SQL patched-version comparison. Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 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 |
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/chrome-remote-desktop/windows.json`:
- Around line 9-12: Recompute and populate the SHA256 for the Chrome Remote
Desktop MSI by downloading the file at the current installer_url
(remoting-host.msi), computing its SHA256 (e.g., using Python hashlib), and
updating the sha256 field value (currently ef977d...) in the JSON so it matches
the freshly computed hash; ensure the computed checksum is non-empty and replace
the existing sha256 string in the windows.json record for this installer_url.
🪄 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: 6c1b4c4e-a25f-485b-93c0-78e2a2bc48c0
📒 Files selected for processing (2)
ee/maintained-apps/outputs/chrome-remote-desktop/windows.jsonee/maintained-apps/outputs/google-chrome/windows.json
| "installer_url": "https://dl.google.com/release2/misc/hxfuhhe6oo55r6utjit63fk764_149.0.7827.18/remoting-host.msi", | ||
| "install_script_ref": "8959087b", | ||
| "uninstall_script_ref": "44518c74", | ||
| "sha256": "9ff875846f3fc5889f195d7b523e6fb6d4c2a0ecfbac9551284d95c62a9342f7", | ||
| "sha256": "ef977db62f6eef33d7b302c2d351589bb6e95c30716bb3eab99d8d7a1695d389", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Verify Chrome Remote Desktop installer URL and SHA256
INSTALLER_URL="https://dl.google.com/release2/misc/hxfuhhe6oo55r6utjit63fk764_149.0.7827.18/remoting-host.msi"
EXPECTED_SHA256="ef977db62f6eef33d7b302c2d351589bb6e95c30716bb3eab99d8d7a1695d389"
echo "Checking URL accessibility..."
HTTP_CODE=$(curl -s -o /dev/null -w "%{http_code}" -I "$INSTALLER_URL")
echo "HTTP Status Code: $HTTP_CODE"
if [ "$HTTP_CODE" != "200" ]; then
echo "ERROR: URL is not accessible (HTTP $HTTP_CODE)"
exit 1
fi
echo "Downloading installer to verify SHA256..."
TEMP_FILE=$(mktemp)
curl -s -L "$INSTALLER_URL" -o "$TEMP_FILE"
echo "Computing SHA256..."
ACTUAL_SHA256=$(sha256sum "$TEMP_FILE" | awk '{print $1}')
rm "$TEMP_FILE"
echo "Expected SHA256: $EXPECTED_SHA256"
echo "Actual SHA256: $ACTUAL_SHA256"
if [ "$EXPECTED_SHA256" = "$ACTUAL_SHA256" ]; then
echo "✓ SHA256 matches!"
else
echo "✗ SHA256 mismatch!"
exit 1
fiRepository: fleetdm/fleet
Length of output: 357
Verify SHA256 for Chrome Remote Desktop installer (URL reachable, checksum still unvalidated)
installer_url in ee/maintained-apps/outputs/chrome-remote-desktop/windows.json (lines 9-12) returns HTTP 200, but the SHA256 check wasn’t performed successfully because sha256sum isn’t available in the verification environment (computed SHA256 is empty). Recompute the downloaded remoting-host.msi SHA256 (e.g., with python/hashlib) and ensure it matches ef977db62f6eef33d7b302c2d351589bb6e95c30716bb3eab99d8d7a1695d389.
🤖 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/chrome-remote-desktop/windows.json` around lines 9
- 12, Recompute and populate the SHA256 for the Chrome Remote Desktop MSI by
downloading the file at the current installer_url (remoting-host.msi), computing
its SHA256 (e.g., using Python hashlib), and updating the sha256 field value
(currently ef977d...) in the JSON so it matches the freshly computed hash;
ensure the computed checksum is non-empty and replace the existing sha256 string
in the windows.json record for this installer_url.
|
Closing in favor of #46704. |
Automated ingestion of latest Fleet-maintained app data.
Summary by CodeRabbit