From f3372b946e182a0bb1d47199ec7087abfb27d34e Mon Sep 17 00:00:00 2001 From: Tony Meyer Date: Thu, 10 Oct 2024 17:55:51 +1300 Subject: [PATCH] ci: disable the automatic ops-scenario releasing (#1415) This hasn't been fully updated to handle the location in the merged repo, but has been enough to wrongly release an `ops.version.version` release (and tag) on merge to main. Disable this for now so that we don't accidentally have another `ops.version.version` release. I'll do a follow-up PR that properly implements ops-scenario releasing alongside ops releases. --- .github/workflows/build_scenario_wheels.yaml | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/.github/workflows/build_scenario_wheels.yaml b/.github/workflows/build_scenario_wheels.yaml index e1666676b..87833841a 100644 --- a/.github/workflows/build_scenario_wheels.yaml +++ b/.github/workflows/build_scenario_wheels.yaml @@ -1,9 +1,13 @@ name: Build ops-scenario wheels +# TODO: adjust this workflow to properly build ops-scenario from the operator repo +# and then this should be adjusted to run when appropriate (not on push to main +# any more, but as part of the releasing workflow we agree on). on: - push: - branches: - - main + workflow_dispatch +# push: +# branches: +# - main jobs: build_wheel: