Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix the release-winget workflow #728

Merged
merged 2 commits into from
Feb 25, 2025
Merged

Fix the release-winget workflow #728

merged 2 commits into from
Feb 25, 2025

Conversation

dscho
Copy link
Member

@dscho dscho commented Feb 21, 2025

This fixes the problem that caused all recent release-winget workflow runs to fail.

This commit changes the workflow to strip the enclosing double quotes
from the PAT.

In a98c3d7 (fixup! Adding winget workflows, 2024-10-28), I
converted the `release-winget` workflow from hard-coding the PAT that is
required as a repository secret to retrieving it from an Azure KeyVault
instead.

However, I made a crucial mistake there: The `az keyvault` call outputs
a JSON-formatted value by default. Using the "tab-separated value"
format as we do elsewhere fixes the problem: There is only one value,
therefore no tab will be inserted, and certainly no double quotes will
surround the retrieved value.

This bug prevented the workflow from running correctly, and Matthew had
to follow the steps manually instead. Let's fix this so that next time,
it will work without any hassle (apart from needing to recreate the PAT
and storing it in the Key Vault because of the PAT's short-lived
nature).

Signed-off-by: Johannes Schindelin <[email protected]>
As we did elsewhere, use the `--output tsv` option of `az keyvault` to
avoid having the retrieved value be enclosed in double quotes.

Signed-off-by: Johannes Schindelin <[email protected]>
@dscho dscho requested a review from mjcheetham February 21, 2025 12:09
@dscho dscho self-assigned this Feb 21, 2025
@dscho
Copy link
Member Author

dscho commented Feb 21, 2025

The CI/win+VS test(1) (push) job is failing with the (somewhat infrequent) "sig_send: error sending signal -72" error that usually goes away when re-running. I'll do that as soon as that's possible (because you have to wait for every last job to finish before you can re-run a job).

@dscho dscho merged commit 5ad6dd6 into vfs-2.48.1 Feb 25, 2025
100 checks passed
@dscho dscho deleted the fix-release-winget branch February 25, 2025 11:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants