delightful-monkey-90700
02/07/2023, 12:28 AMpulumi
from source (v3.54.0) and it attempts to download something as part of the build step without verifying that what it fetched was what it intended to fetch:
+ curl -OL --fail <https://github.com/pulumi/watchutil-rs/releases/download/v0.1.4/pulumi-watch-v0.1.4-x86_64-unknown-linux-gnu.tar.gz>
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (7) Couldn't connect to server
(it fails since it's part of the build step, and building is done offline)orange-policeman-59119
02/07/2023, 3:15 AMdelightful-monkey-90700
02/07/2023, 5:00 PMorange-policeman-59119
02/07/2023, 5:43 PMpulumi[.exe]
but not any language plugins.delightful-monkey-90700
02/07/2023, 5:46 PMorange-policeman-59119
02/07/2023, 5:46 PMmake
targets to package the CLI in an efficient manner. For example, until very very recently to work around bugs in cross-compiling to macOS, we built the macOS targets on macOS and combined them in GitHub Actions.delightful-monkey-90700
02/07/2023, 5:47 PMorange-policeman-59119
02/07/2023, 5:48 PMAdd documentation on how to create a correct, complete, and proper release;I don't know if we're at a point where our processes are stable enough or self-contained enough to document that. Like I said with respect to cross-compiling for macOS, our build process required multiple workers on different OSes until recently. We can't rule out that a change in Golang forces us to do the same in the future.
1. Add a test step which validates at the very least the existence of all the requisite componentsI think @worried-rain-74420, on the team that manages the CLI releases, would very much agree. The bug reports we've seen because of improper packaging of the CLI have frustrated users.
delightful-monkey-90700
02/07/2023, 5:54 PMorange-policeman-59119
02/07/2023, 7:48 PMgoreleaser
.