Files
Allen Houchins e1c7d71ede Use JetBrains build numbers in FMA patch policies on Windows (#47484)
JetBrains NSIS installers write the build number (e.g. 252.28238.7) as
the registry DisplayVersion, while the winget PackageVersion is the
marketing version (e.g. 2025.2.5). The auto-generated patch policy
compared osquery's programs.version (build number) against the marketing
version, so up-to-date installs always failed the policy and queued
unnecessary reinstalls.

Opt the 12 JetBrains IDE FMAs into use_display_version_for_patch so the
patch policy compares against the build number published in the winget
manifest's AppsAndFeaturesEntries. JetBrains Toolbox is excluded: its
manifest has no DisplayVersion and it is not affected.

Fixes #47478
2026-06-11 21:47:08 -05:00

15 lines
520 B
JSON

{
"name": "PhpStorm",
"slug": "phpstorm/windows",
"package_identifier": "JetBrains.PhpStorm",
"unique_identifier": "PhpStorm",
"fuzzy_match_name": true,
"use_display_version_for_patch": true,
"install_script_path": "ee/maintained-apps/inputs/winget/scripts/phpstorm_install.ps1",
"uninstall_script_path": "ee/maintained-apps/inputs/winget/scripts/phpstorm_uninstall.ps1",
"installer_arch": "x64",
"installer_type": "exe",
"installer_scope": "machine",
"default_categories": ["Developer tools"]
}