Open pljones opened 1 month ago
I don't think they are related. I believe there's something wrong in two places.
For 1, the cleanest way would be to call gh release upload in the respective scripts instead of the hacky cross platform method we use currently:
The issue is Windows: https://github.com/cli/cli/issues/5099
Otherwise, we could just upload every file from the deploy directory with a wildcard.
For 2, further investigation is needed.
I think for now we'll just split the release upload into two artifacts again.
Concerning 2, it seems to be comparable to https://github.com/actions/setup-node/issues/362
Maybe we need to use a non standard location to put Qt to, or just delete the cache.
OK, as it doesn't appear to have a discernable negative effect, I'm bumping the problem to after the release.
Describe the bug
When editing the 3.11.0rc1 release, I noticed the following error:
Probably something in the deployment scripts.
There's also a warning relating to macOs in the output: but may not be related.
To Reproduce
Cut a release candidate.
Expected behavior
No errors
Version of Jamulus
3.11.0rc1 release build.