Publishing v3.74.0 to npm failed with `../../scripts/publish_npm.sh: line 13: my_array[2]: unbound variable`.
This commit temporarily changes the `publish_npm.sh` script to not have the unbound variable and comments out jobs in the release workflow that already succeeded, and adds a way to manually dispatch the release workflow to unblock the release. Will use that to re-run the release workflow.
Afterwords, we can revert and address the actual issue.
We have a few places in CI where we use action-install-gh-release
to download and install specific or latest binary releases of a
dependency.
Nearly all these steps, besides the one in ci-test-codegen,
were unauthenticated.
This caused us to run into rate limits with the GitHub API
when trying to get the latest release and resulted in delays like:
```
Run jaxxstorm/action-install-gh-release@v1.7.1
==> System reported platform: linux
==> Using platform: linux
==> System reported arch: x64
==> Using arch: x64
Warning: RateLimit detected for request GET /repos/{owner}/{repo}/releases/tags/{tag}.
Retrying after 3300 seconds.
Error: The operation was canceled.
```
This sets GITHUB_TOKEN for all instances of this step
so that we're less likely to get rate limited by GitHub on this.
* fix: handle exception for main not found in python (#10617)
Improve error message when pulumi-python cannot find a main program.
* Bump golangci-lint version to v1.47.3
Co-authored-by: stefins <stefin2016@gmail.com>
* dotnet program-gen targets .NET 6
* changelog entry
* Update GH workflows to use .NET 6
* Enable DOTNET_ROLL_FORWARD=Major for GH workflows
* Expose GeneratePrograms with ability to provide generation options. Use specialized options for import
* Bump dotnet test projects TFM and relax warnings as errors
* refactor code according to Ian's comments
* Include error in generator diagnostics when unable to find function schema
* remove specialized version of GenerateProgram for import and refactor lowerExpression
* remove AcceptCodegenChanges from program driver
* dotnet integration tests updated to net6.0
* Generate return await on top-level Deployment.RunAsync
* Start simplifying build.yml
* Use updated code
* Split goreleaser build files by OS
* Fixup PR goreleaser-flags
* Try to fix test.yml downloading of binaries
* Copy test.yml changes to test-fast.yml
* Goreleaser file format
* Use prebuilt builder in .goreleaser*.yml
* Do not tidy in prep-for-goreleaser.sh
* Fix build.yml args
* Update publish-binaries and how it is called
* Use local test-fast.yml in master.yml
* Set GORELEASER_KEY
* Drop PREBUILT support from go-wrapper
* Restore executable bit on downloaded artifacts
* Cache restore-key and comment fix
* Reset cache key to get smaller caches
* Workaround: manually install pulumi-language-python-exec script
* Unify build files
* Fix env syntax
* Fix test.yml GHA-isms
* Fix bad merge
* Dedicated workflow publish-binaries.yml
* Use factored out code in master.yml
* Use factored out code in prerelease.yml
* Use factored out code in release.yml
* Small consistency fixes
* Do not specify platform
* Inspect logs
* Compensate for goreleaser 1.8.3 amd64_v1 trick
* Revert run-build-and-acceptance-tests changes
* Remove temp branch name
* Spacing
* Inherit secrets
* Explicit secret passing to pass actions lint
* Do not rebuild Go binaries in release.yml, use testsed builds
* Ensure checksum mismatch blocks partial releases (side-effects)
* Install goreleaser-filter in the right job
* Remove windows-build
* Factor out test.yml
* Factor out build.yml an test.yml everywhere
* Verify checksums after releasing
* Split out test-fast.yml
* Use test-fast.yml in PRs
* Fix master checksums check
* Revert python->python3 default switch, limit to CI
We've had a few issues in the recent past related to pipenv oddities in
CI which lead us to temporarily globally install the Python SDK in CI.
This change removes the use of pipenv in favor of Python's built-in
venv and avoids globally installing the Python SDK.