Submit Bookworm to winget

[cary-rowen]

Is your feature request related to a problem? Please describe.

While we have an automated release process for Bookworm, including a draft feature that ensures thorough review before publishing, the current workflow does not include automated submission to Winget.

Describe the solution you'd like

I propose extending the existing GitHub Actions workflow to include an automated step for submitting Bookworm to Winget once a draft release is published. The solution would involve the following steps:

1. Detect Published Release: Modify the existing workflow to trigger an additional step when a draft release is published. This can be achieved by using the published event in the workflow's trigger conditions.

2. Generate Winget Manifest: Use a tool like wingetcreate to automatically generate the Winget manifest file based on the release details. This step should be integrated into the workflow to ensure that the manifest is created immediately after the release is published.

3. Validate Manifest: Implement a validation step to ensure that the generated manifest meets all Winget requirements. This can include checks for correct formatting, valid URLs, and accurate metadata.

4. Create Pull Request in Winget Repository: Automatically open a pull request on the Winget repository with the updated manifest file. The pull request should include a descriptive message detailing the changes and the version of Bookworm being submitted.

Describe alternatives you've considered

• Manual Submission: This approach is less efficient and more error-prone.
• Separate Automation Workflow: Create a separate GitHub Actions workflow specifically for Winget submissions.

Additional context

Automating the submission to Winget will enhance the efficiency of the release process, ensuring that Bookworm users can access the latest version as soon as it is published. This integration will also reduce the risk of errors and improve the overall user experience for those who rely on Winget for software management.

[mush42]

@cary-rowen this is very cool to have and it'll minimize friction a lot by having a good distribution channel besides GitHub.