mirror of https://github.com/pulumi/pulumi.git
1af5605e27
Currently we have a prepare-release step in the on-pr workflow. This step updates the draft release that we're using to release pulumi/pulumi. It is only run when the `ci/test` label is added to a PR, which is done very rarely, but definitely has happened before. This could in theory lead to the wrong/unreviewed code being released, if someone adds a ci/test label to a PR, and no other PR is merged between that and a freeze PR is merged (note that the freeze PR will not update the draft release, but will create the next release). I think our prepare-release workflow is stable enough that we don't need to test it in CI at this point, and we should never run the risk of releasing unreviewed code. Therefore remove this step completely from the on-pr CI workflow. |
||
---|---|---|
.. | ||
ci-build-binaries.yml | ||
ci-build-sdks.yml | ||
ci-dev-release.yml | ||
ci-info.yml | ||
ci-lint.yml | ||
ci-performance-gate.yml | ||
ci-prepare-release.yml | ||
ci-run-test.yml | ||
ci-test-docs-generation.yml | ||
ci.yml | ||
command-dispatch.yml | ||
cron-direct-build.yml | ||
download-pulumi-cron.yml | ||
on-community-pr.yml | ||
on-merge.yml | ||
on-pr-close.yml | ||
on-pr-default.yml | ||
on-pr.yml | ||
on-push.yml | ||
on-release.yml | ||
pr-test-acceptance-on-dispatch.yml | ||
pr-test-codegen-downstream.yml | ||
pr-test-docs-gen-on-pr.yml | ||
pr-test-docs-generation-on-dispatch.yml | ||
rebase.yml | ||
release-homebrew-tap.yml | ||
release-pr.yml | ||
release.pub | ||
release.yml | ||
sign.yml | ||
trigger-homebrew-event.yml | ||
trigger-release-docs-event.yml |