Bump deepctl to 0.2.23#5
Merged
Merged
Conversation
Merged
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
1 participant
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.
Manual bump from deepgram/cli@v0.2.23. The automated release run failed — the new JSON-API watch step (deepgram/cli#70) passed, but
bump_brew_formula.py's own internalpip install deepctl==0.2.23hit the PyPI simple-index lag (the same one called out in #70's PR body as the next escalation). Sentinel sdist sha256:f2918a73f97331660afd2b58295a4a394b0ad5f7728de6649323997205c1ee58(matches PyPI JSON API). Generated identically to automation viascripts/bump_brew_formula.py+homebrew-pypi-poet. If this PR breaksbrew testorbrew install, do not edit the formula directly — fix the template inscripts/templates/deepgram.rb.templateand let the next release regenerate it.