feat: add batch-change release.yaml for automation #703
Conversation
This file contains hidden or 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
jdpleiness
approved these changes
Jun 26, 2025
Chickensoupwithrice
force-pushed
the
al/add-batch-change-release.yaml
branch
from
8eaf8ca to
e5b74ae
Compare
enriquegh
pushed a commit
that referenced
this pull request
Jul 10, 2025
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 - [ ] Follow the [manual testing process](https://github.com/sourcegraph/deploy-sourcegraph-helm/blob/main/TEST.md) - [ ] Update [changelog](https://github.com/sourcegraph/deploy-sourcegraph-helm/blob/main/charts/sourcegraph/CHANGELOG.md) - [ ] Update [Kubernetes update doc](https://docs.sourcegraph.com/admin/updates/kubernetes) ### Test plan Run batch change temporal workflow <!-- As part of SOC2/GN-104 and SOC2/GN-105 requirements, all pull requests are REQUIRED to provide a "test plan". A test plan is a loose explanation of what you have done or implemented to test this, as outlined in our Testing principles and guidelines: https://docs.sourcegraph.com/dev/background-information/testing_principles Write your test plan here after the "Test plan" header. -->
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
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 directorysg ops update-imagesruns from. I also had to remove references togitandghChecklist
Test plan
Run batch change temporal workflow