Automating the make release for task-processing - COMPINFRA-3567#229
Merged
Conversation
e3b9154 to
34182d0
Compare
nemacysts
approved these changes
May 14, 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
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.
automating the release process for this repo since its currently manual. We used to follow these steps before manually:
then wait for jenkins to push the new release to pypi
Testing
make releaseto see if it will fail with a warning and it did:make release. It should fail and it did:make releaseon the current tag and it failed with :output of make release: https://fluffy.yelpcorp.com/i/jlhvf5RBXPXSpFsmRZcBNcQgv529BPSz.html
and
and