Mozilla.Firefox-msix version 94.0.0.0

[oxygen-dioxide]

• Have you signed the Contributor License Agreement?
• Have you checked that there aren't other open pull requests for the same manifest update/change?
• 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.0 schema?

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

---

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

   

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[jedieaston]

Why can't this just be part of the Mozilla.Firefox manifest?

[oxygen-dioxide]

Why can't this just be part of the Mozilla.Firefox manifest?

The version number format of this msix package is different from the Mozilla.Firefox manifest. For example, Mozilla.Firefox 94.0 is Mozilla.Firefox-msix 94.0.0.0

[jedieaston]

That's true, but due to Firefox's versioning scheme it shouldn't matter in practice (they only use to the second decimal point for any release), it shouldn't matter (94.0.0.0 would upgrade to 94.0.1 in winget's logic).

[OfficialEsco]

That's true, but due to Firefox's versioning scheme it shouldn't matter in practice (they only use to the second decimal point for any release), it shouldn't matter (94.0.0.0 would upgrade to 94.0.1 in winget's logic).

WinGet also "ignore"/remove zero's, so if we flipped the numbers 94.0.0.0 would not show up as a upgrade for version 94.0 (Its just good practice to keep the 0's if the versions are the same)
This can also be corrected in Manifest Version 1.1 with ease since the msix dosn't break winget

[oxygen-dioxide]

#34147

[oxygen-dioxide]

Why can't this just be part of the Mozilla.Firefox manifest?

Then how can I choose which package to install between the exe package and the msix package?

[ItzLevvie]

Added in #34147?