Skip to content

Commit

Permalink
ci: disable the automatic ops-scenario releasing (canonical#1415)
Browse files Browse the repository at this point in the history
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.
  • Loading branch information
tonyandrewmeyer authored Oct 10, 2024
1 parent 2d6ab02 commit f3372b9
Showing 1 changed file with 7 additions and 3 deletions.
10 changes: 7 additions & 3 deletions .github/workflows/build_scenario_wheels.yaml
Original file line number Diff line number Diff line change
@@ -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:
Expand Down

0 comments on commit f3372b9

Please sign in to comment.