Skip to content

Stop the triphthong handler writing to stdout, publish from CI - #8

Merged
neburnodrog merged 1 commit into
mainfrom
fix/stray-print-and-release
Oct 3, 2026
Merged

neburnodrog merged 1 commit into
mainfrom
fix/stray-print-and-release

Conversation

@neburnodrog

Copy link
Copy Markdown
Owner

Two things 2.0.0 should not ship without.

tripthong_parser printed its input. Any verse containing a triphthong leaked a line into the CLI report:

$ pyverse "esternohioideo"
i-oi
        Syllabified Text | -es-ter-no-hioi-de-o

The existing test that pins the CLI to four lines used a verse with no triphthong, so it never caught this. It now has a sibling that uses one. The snapshot recorder no longer has to redirect stdout to keep its own output clean.

release.yml publishes to PyPI on a published GitHub release, through trusted publishing. No token is stored in the repository or on anyone's machine; the workflow mints a short-lived one. It builds, runs twine check, and uploads from the pypi environment.

Before the first release, the trusted publisher has to exist on PyPI: owner neburnodrog, repository Pyverse, workflow release.yml, environment pypi.

🤖 Generated with Claude Code

tripthong_parser printed its input, so any verse with a triphthong leaked a
line into the CLI report. The CLI test that pins the report to four lines used
a verse without a triphthong; it now has a sibling that uses one. The snapshot
recorder no longer needs to redirect stdout.

release.yml publishes to PyPI on a published GitHub release, through trusted
publishing, so no token is stored in the repository or on a developer machine.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@neburnodrog
neburnodrog merged commit fa0256b into main Oct 3, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant