ci: add manual pre-release workflow for v3 branch#11336
Merged
Conversation
Adds a workflow_dispatch-only workflow that builds and publishes a haystack-ai pre-release from the v3 branch to PyPI, mirroring the existing nightly workflow but without the scheduled cron trigger. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
Code reviewNo issues found. Checked for bugs and CLAUDE.md compliance. |
sjrl
approved these changes
May 19, 2026
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
2 participants
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
Closes https://github.com/deepset-ai/haystack-private/issues/357
Proposed Changes:
workflow_dispatch-only workflow (.github/workflows/v3_pypi_release.yml) that builds and publishes ahaystack-aipre-release from thev3branch to PyPInightly_testpypi_release.ymlworkflow but without the scheduled cron trigger — releases are manual only-rcNsuffix fromVERSION.txtand appends.devYYYYMMDDHHMMSSfor a unique PEP 440 pre-release identifierHow did you test it?
Will test via manual trigger once merged and once we have meaningful changes on the v3 branch
Notes for the reviewer
I enabled branch protection rules on GitHub for v3 and configured trusted publishing for this new workflow on pypi. I updated VERSION.txt file on the v3 branch already.
I decided not to trigger nightly pre-releases automatically for v3 yet to reduce noise. We can enable that later once useful.
Checklist
fix:,feat:,build:,chore:,ci:,docs:,style:,refactor:,perf:,test:and added!in case the PR includes breaking changes.