quarto-dev / quarto-dev/quarto-release-bundles
Automate winget release
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 3
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Process needs to be manual because wingetcreate can't be use due to limitation as we are using two scope in our manifest with one url. See https://github.com/microsoft/winget-create/issues/166 and https://github.com/microsoft/winget-create/issues/291 (cc @dpprdan)
Also, it can't be used interactively either due to this.
For now, I am doing manual update using YAMLCreate.ps1 in winget-pks repo.
We could try modifying the manifests manually to automate, but probably more work than doing update manually, until they solve the issue.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the current manual update process in YAMLCreate.ps1 in the winget-pks repository and review the linked wingetcreate limitations. Examine the manifests' two-scope, one-URL setup and determine whether manual manifest modification can be automated. Done means the winget release update no longer requires the current manual process.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100