fleet/ee/maintained-apps/inputs/winget/1password.json

{
  "name": "1Password",
  "slug": "1password/windows",
  "package_identifier": "AgileBits.1Password",
  "unique_identifier": "1Password",
  "installer_arch": "x64",
  "installer_type": "msi",
  "installer_scope": "machine",
  "default_categories": ["Productivity"],
  "uninstall_script_path": "ee/maintained-apps/inputs/winget/scripts/1password_uninstall.ps1",
  "program_publisher": "Agilebits Inc."
}
Adding 1Password for Windows as an FMA (#35835) Adding the Windows version of 1Password to our Fleet Maintained App Catalog. --------- Co-authored-by: Allen Houchins <32207388+allenhouchins@users.noreply.github.com> 2025-11-20 16:36:46 +00:00			`{`
			`"name": "1Password",`
			`"slug": "1password/windows",`
			`"package_identifier": "AgileBits.1Password",`
			`"unique_identifier": "1Password",`
			`"installer_arch": "x64",`
			`"installer_type": "msi",`
			`"installer_scope": "machine",`
Improve 1Password uninstall reliability and add timeout (#36111) Added a new PowerShell uninstall script for 1Password with process termination, registry checks, logging, and timeout handling. Updated the template uninstall script by adding timeout protection to generic MSI uninstall scripts to prevent hangs. These changes improve reliability and diagnostics for uninstall operations. <!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> Related issue: Resolves # # Checklist for submitter If some of the following don't apply, delete the relevant line. - [ ] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. See [Changes files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/guides/committing-changes.md#changes-files) for more information. - [ ] Input data is properly validated, `SELECT *` is avoided, SQL injection is prevented (using placeholders for values in statements) - [ ] If paths of existing endpoints are modified without backwards compatibility, checked the frontend/CLI for any necessary changes ## Testing - [ ] Added/updated automated tests - [ ] Where appropriate, [automated tests simulate multiple hosts and test for host isolation](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/reference/patterns-backend.md#unit-testing) (updates to one hosts's records do not affect another) - [ ] QA'd all new/changed functionality manually For unreleased bug fixes in a release candidate, one of: - [ ] Confirmed that the fix is not expected to adversely impact load test results - [ ] Alerted the release DRI if additional load testing is needed ## Database migrations - [ ] Checked schema for all modified table for columns that will auto-update timestamps during migration. - [ ] Confirmed that updating the timestamps is acceptable, and will not cause unwanted side effects. - [ ] Ensured the correct collation is explicitly set for character columns (`COLLATE utf8mb4_unicode_ci`). ## New Fleet configuration settings - [ ] Setting(s) is/are explicitly excluded from GitOps If you didn't check the box above, follow this checklist for GitOps-enabled settings: - [ ] Verified that the setting is exported via `fleetctl generate-gitops` - [ ] Verified the setting is documented in a separate PR to [the GitOps documentation](https://github.com/fleetdm/fleet/blob/main/docs/Configuration/yaml-files.md#L485) - [ ] Verified that the setting is cleared on the server if it is not supplied in a YAML file (or that it is documented as being optional) - [ ] Verified that any relevant UI is disabled when GitOps mode is enabled ## fleetd/orbit/Fleet Desktop - [ ] Verified compatibility with the latest released version of Fleet (see [Must rule](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/workflows/fleetd-development-and-release-strategy.md)) - [ ] If the change applies to only one platform, confirmed that `runtime.GOOS` is used as needed to isolate changes - [ ] Verified that fleetd runs on macOS, Linux and Windows - [ ] Verified auto-update works from the released version of component to the new version (see [tools/tuf/test](../tools/tuf/test/README.md)) 2025-11-21 04:45:39 +00:00			`"default_categories": ["Productivity"],`
Fix 1Password Windows publisher name capitalization (#37946) ## Summary Fixes the publisher name in the 1Password Windows Fleet-maintained app query to match the actual Windows registry value. ## Issue The generated query was using `AgileBits Inc.` (capital 'B') from the winget manifest, but Windows registry shows the publisher as `Agilebits Inc.` (lowercase 'b'). This caused a mismatch preventing Fleet from properly matching the installed software with the Fleet-maintained app. ## Changes - Added `program_publisher` override to `inputs/winget/1password.json` with the correct publisher name - Regenerated output manifest with corrected query ## Test plan - [x] Verify the query matches actual Windows registry value on a test host - [x] Confirm Fleet can now properly match installed 1Password software 2026-01-07 14:59:26 +00:00			`"uninstall_script_path": "ee/maintained-apps/inputs/winget/scripts/1password_uninstall.ps1",`
			`"program_publisher": "Agilebits Inc."`
Adding 1Password for Windows as an FMA (#35835) Adding the Windows version of 1Password to our Fleet Maintained App Catalog. --------- Co-authored-by: Allen Houchins <32207388+allenhouchins@users.noreply.github.com> 2025-11-20 16:36:46 +00:00			`}`