Fix Genesys Cloud FMA: winget dropped x86, ship x64 MSI - #50742
Conversation
Genesys.GenesysCloud 2.53.923.0 stopped publishing x86 installers and now ships only an x64 wix MSI. The input was pinned to installer_arch x86, so the nightly ingestion job panicked with 'failed to find installer for app'. Flip the input to x64 and regenerate the output (2.51.916.0 -> 2.53.923.0). Queries and install/uninstall scripts are unchanged; the UpgradeCode is the same, so the x64 MSI upgrades existing x86 installs in place.
GitHub Actions
Inactive
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
WalkthroughThe Genesys Cloud Winget configuration now targets the x64 installer. The Windows package metadata now references version Possibly related PRs
✨ 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.
Pull request overview
Updates the Genesys Cloud Windows Fleet-maintained app (FMA) to match upstream winget changes where the vendor no longer publishes an x86 installer, preventing the winget ingester from filtering out the only available installer and panicking.
Changes:
- Switch the winget input
installer_archfromx86tox64forGenesys.GenesysCloud. - Regenerate the Windows output manifest to the latest upstream version (2.53.923.0), including updated installer URL and SHA256 and updated
patchedversion floor.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| ee/maintained-apps/inputs/winget/genesys-cloud.json | Changes installer_arch to x64 so the ingester selects the available upstream installer. |
| ee/maintained-apps/outputs/genesys-cloud/windows.json | Updates the pinned version, patched query version floor, installer URL, and SHA256 to the new x64 MSI release. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Checklist for submitter
If some of the following don't apply, delete the relevant line.
SELECT *is avoided, SQL injection is prevented (using placeholders for values in statements), JS inline code is prevented especially for url redirects, and untrusted data interpolated into shell scripts/commands is validated against shell metacharacters.Testing
Details
The nightly maintained-apps ingestion job panicked with
failed to find installer for appon Genesys Cloud:Why
Genesys.GenesysCloud 2.53.923.0 stopped publishing x86 installers upstream. Previous versions (e.g. 2.51.916.0) shipped two x86 installers (a burn
.exeand a wix.msi); the latest manifest ships only a single x64 wix MSI. Our input pinnedinstaller_arch: "x86", so the ingester filtered out the only available installer and panicked.What changed
ee/maintained-apps/inputs/winget/genesys-cloud.json:installer_archx86→x64ee/maintained-apps/outputs/genesys-cloud/windows.json: regenerated withgo run ./cmd/maintained-apps -slug genesys-cloud/windows— version 2.51.916.0 → 2.53.923.0, installer URL now the x64 MSI, sha256 matches the winget manifest'sInstallerSha256Notes for reviewers
name = 'GenesysCloud',publisher = 'Genesys Inc.'), and install/uninstall script refs are identical since it's still a machine-scope MSI — detection and remediation carry over for existing installs.UpgradeCodeis unchanged upstream ({A0E8C487-C337-441C-83AF-90364DA4B793}), so the x64 MSI upgrades existing x86 installs in place (ProductCode is new, install dir moves fromProgramFiles(x86)toProgramFiles).Microsoft.VCRedist.2015+.x64dependency (the old x86 MSI declared the x86 variant). Fleet doesn't resolve winget dependencies; the FMA validator run on this PR will confirm whether the installer tolerates its absence.Summary by CodeRabbit