Repository navigation
ci: Release orchestration workflow - #10233
Merged
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
anakin87
marked this pull request as ready for review
December 12, 2025 10:50
anakin87
requested review from
mpangrazzi and
vblagoje
and removed request for
a team and
vblagoje
December 12, 2025 10:50
mpangrazzi
reviewed
Dec 12, 2025
Contributor
There was a problem hiding this comment.
Looks good! I think it could be also nice to add:
concurrency:
group: release
cancel-in-progress: falseto release.yml.
This will prevent two release workflows to run concurrently, which may happen accidentally. With this, the second one will be always queued.
Member
Author
Good idea! Added in 9af422b |
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
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.
Related Issues
Proposed Changes:
Add a release orchestration workflow. This acts as a higher level API over the current manual release process.
It is meant to be invoked using
gh workflow run release.yml -R deepset-ai/haystack -f version=v2.99.0-rc1.How did you test it?
Extensively tested on my fork.
In any case, I'd like to test this firsthand in the first automated release (something might be off with GitHub tokens permissions).
Notes for the reviewer
In the end, I decided to create another script to prepare the release notification, to avoid overcomplicating the main workflow.
Checklist
fix:,feat:,build:,chore:,ci:,docs:,style:,refactor:,perf:,test:and added!in case the PR includes breaking changes.