kiwix.kiwixjs version 1.3.2.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]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[Jaifroid]

@oxygen-dioxide Thank you for submitting Kiwix JS Windows to the WinGet repo. As the developer of Kiwix JS Windows, I was about to do the same thing, when I saw your submission. I note you've put as the package URL the permalink. I think this might be an issue because when I update the package, the permalink will change and so will the SHA. This will cause installation errors. I think it would be better for me to create this submission using the GitHub repository instead, which is versioned. I will also be able to add the proper locale data.

Could you close this PR without merging, and I will create one, which I can then keep up to date as part of the package creation script?

Many thanks.

[Jaifroid]

@oxygen-dioxide please see PR #16135 which I have created with a properly versioned package.

[denelon]

@Jaifroid you might want to take a look at https://github.com/microsoft/winget-create. It is still a very early preview, but was designed with CI/CD scenarios in mind to help automate the process of generating manifests and submitting PRs for these packages. We also have a feature in progress for "verified publisher(s)" to prevent others from making changes to manifests. The current thinking is to inform the author of the PR (and possibly the verified owner). Then the bot would close the PR.

[Jaifroid]

@denelon I actually did use winget-create for the PR that replaces this one: #16135 . I'll be using it in CI/CD for sure.