ci: fix Windows gh release pipeline #165
Conversation
|
Backports to the stable branch are to be avoided unless absolutely necessary for fixing bugs, security issues, and perf regressions. Changes intended for backport should be structured such that a minimum effective diff can be committed separately from any refactoring, plumbing, cleanup, etc that are not strictly necessary to achieve the goal. Any of the latter should go only into master and ride the normal stabilization schedule. |
|
Backports to the beta branch are to be avoided unless absolutely necessary for fixing bugs, security issues, and perf regressions. Changes intended for backport should be structured such that a minimum effective diff can be committed separately from any refactoring, plumbing, cleanup, etc that are not strictly necessary to achieve the goal. Any of the latter should go only into master and ride the normal stabilization schedule. Exceptions include CI/metrics changes, CLI improvements and documentation updates on a case by case basis. |
(cherry picked from commit 3863bb1)
(cherry picked from commit 3863bb1)
(cherry picked from commit 3863bb1)
(cherry picked from commit 3863bb1)
… of #165) (#166) ci: fix Windows gh release pipeline (#165) (cherry picked from commit 3863bb1) Co-authored-by: Yihau Chen <[email protected]>
… of #165) (#167) ci: fix Windows gh release pipeline (#165) (cherry picked from commit 3863bb1) Co-authored-by: Yihau Chen <[email protected]>
As CI will stop on the first error, this simplifies debugging as in most cases the output will contain a more verbose error description.
2 participants
Problem
the Windows artifacts doesn't upload to the gh release page
Summary of Changes
use the correct download path