Plan B: PyPI distribution + 1.0.0 release (#49) - #50
Merged
Conversation
Adds license, authors, homepage/repository/documentation URLs, keywords, classifiers (incl. Development Status: 5 - Production/Stable for the 1.0.0 release this PR ships), and Issues/Changelog URLs. Wheel builds clean and passes `twine check`. Refs #49 Co-Authored-By: Claude <noreply@anthropic.com>
Every PR must add a CHANGELOG.md `[Unreleased]` entry, OR bump the pyproject.toml version with a matching `[<version>]` section. Dependabot PRs are skipped via GITHUB_ACTOR check. Refs #49 Co-Authored-By: Claude <noreply@anthropic.com>
release.yml triggers on push to main, detects version bumps via tag-existence check, runs tests, builds wheel + sdist, publishes via PyPI Trusted Publishing (OIDC), tags v<version>, and creates a GitHub Release with notes pulled from CHANGELOG.md by bin/changelog-section. Refs #49 Co-Authored-By: Claude <noreply@anthropic.com>
Strips feature walkthroughs (now on the docs site at jayravaliya.com/tenor-tui/) and reorients around install + develop + contribute. Adds PyPI / CI / Python / License badges. Under 80 lines. Refs #49 Co-Authored-By: Claude <noreply@anthropic.com>
First stable PyPI release. Promotes [Unreleased] to [1.0.0] in CHANGELOG. Closes #49 Co-Authored-By: Claude <noreply@anthropic.com>
This was referenced Apr 27, 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
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.
Summary
Second half of the umbrella shipping push (#45). Ships TenorTUI 1.0.0 to PyPI.
5 commits, each phase a discrete change:
e0397d7PyPI metadata + MIT LICENSE — wheel passestwine check5112c08bin/check-version-bump+ CI gate — every PR needs a CHANGELOG entry or version bump106b6c3release.ymlworkflow +bin/changelog-section— auto-publish to PyPI via OIDC, tag, GitHub Release022c7c7README rewrite — under 80 lines, dev/install/contribute focus, points at docs sitebd10b49Bump to 1.0.0 — promotes[Unreleased]to[1.0.0]in CHANGELOGWhat happens on merge
release.ymltriggers on push to main, detects the version bump (nov1.0.0tag exists yet), runs tests, builds the wheel, publishes to PyPI via Trusted Publishing (no API tokens), tagsv1.0.0, and creates a GitHub Release with the wheel + sdist attached.The deploy of the docs site has already happened on the previous merge — Pages is live at https://jayravaliya.com/tenor-tui/.
Test plan
make docs-strictpassespoetry buildproduces clean wheel + sdist;twine checkPASSEDbin/check-version-bumppasses locally (recognizes 1.0.0 bump + matching CHANGELOG section)bin/changelog-section 1.0.0returns the right bodypip install tenor-tuiworks after releaseManual prerequisites (already done)
jayrav13/tenor-tui+release.yml+releaseenvironmentreleaseexists on the repotenor-tuiavailableCloses #49.
Co-authored by Claude