scripts/publish: fix sh-incompatible &> redirect (why the 0.2.7 Publish run failed) - #29
Merged
Merged
Conversation
The script runs under #!/bin/sh; on dash `&>` is not a redirection operator, so the `command -v twine` check misparses and the "Unable to find twine" branch fires even when twine is installed. This is why the Publish workflow failed on the 0.2.7 tag (the runner had twine — its path is visible in the run log — yet the job exited 1). start_pulsar keeps its `&>`: it declares #!/bin/bash. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Nxg7e1Jtk5qykAdYoYENdw
omer9564
approved these changes
Aug 20, 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.
The publish workflow's failure on tag 0.2.7 was not a missing dependency: twine was installed (its path is line 15 of the run log).
scripts/publishruns under#!/bin/sh, and dash does not implement the bash-only&>operator, socommand -v twine &>/dev/nullmisparses and the not-found branch fires unconditionally. Replaced both occurrences with>/dev/null 2>&1. (scripts/start_pulsarkeeps its&>— it declares#!/bin/bash.)With this + a valid
PYPI_TOKENsecret, the next tag push should publish cleanly.🤖 Generated with Claude Code
https://claude.ai/code/session_01Nxg7e1Jtk5qykAdYoYENdw