ci: disable the automatic ops-scenario releasing #1415
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
benhoyt
approved these changes
Oct 10, 2024
|
I'm going to merge this without further review to avoid another |
Thanks! I deleted the one (release and tag) that I triggered when merging the doc PR. In the few short hours since we did the repo merge I forgot that it would happen 😞. |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This hasn't been fully updated to handle the location in the merged repo, but has been enough to wrongly release an
ops.version.versionrelease (and tag) on merge to main.Disable this for now so that we don't accidentally have another
ops.version.versionrelease. I'll do a follow-up PR that properly implements ops-scenario releasing alongside ops releases.