feat: add release.yaml specific for batch changes #291
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.
Description
Since we're dependent on batch-changes for pr creation now (given it doesn't clone the .git files so we can't create PRs from execution phase) we have to modify the release.yaml. Instead of breaking existing workflows, we're creating a new release.yaml here eventually to be deprecated. I tested this yesterday on the docker repo, and it worked fine, so I'm replicating that here.
It's a direct copy of the release.yaml, except since it's in a subdir, it needs to change the directory sg ops update-images runs from. I also had to remove references to git and gh
Checklist
Test plan
run batch change temporal workflow