New version: jm2.Tributary version 0.2.1

[jm2]

Checklist for Pull Requests

• Have you signed the Contributor License Agreement?
• Is there a linked Issue? If so, fill in the Issue number below.
  • Resolves #[Issue Number]

Manifests

• Have you checked that there aren't other open pull requests for the same manifest update/change?
• This PR only modifies one (1) manifest
• Have you validated your manifest locally with winget validate --manifest <path>?
• Have you tested your manifest locally with winget install --manifest <path>?
• Does your manifest conform to the 1.12 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

---

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-136-355588-20260405-1

[jm2]

Is this actually a failure on my end or just a validation pipeline failure?

[Trenly]

@wingetbot run

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-138-355588-20260413-1

[stephengillie]

Automatic Validation ended with:

Installation failed with exit code -2147467260

Hex	Dec	Inverted Dec	Symbol	Description
80004004	-2147467260	2147500036	E_ABORT	Operation Aborted

(Automated response - build 1247.)

[jm2]

I believe the validation failure here might be for the upgrade case because we switched to using a proper AppId in the InnoSetup. Considering the minimal install base at this point and the early alpha version, this should be safe to push and I'll make any users aware if upgrades fail. So far the installer has been manually tested successfully.

[stephengillie]

@wingetbot run

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-138-355588-20260414-1

[wingetbot]

Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present.