Repository navigation
Release 0.8.0 - #47
Merged
Merged
Conversation
vringar
force-pushed
the
release/0.8.0
branch
from
September 5, 2026 19:56
9280efd to
c16b58f
Compare
Set the version and date the changelog section so the tag can be cut. release.yml refuses to publish if the tag does not match __version__, or if the changelog section for it is still undated. Also correct the environment guidance in docs/release.rst, which suggested restricting the pypi environment to the master branch and to tags. The workflow only triggers on a tag push, so a branch rule can never apply.
vringar
force-pushed
the
release/0.8.0
branch
from
September 5, 2026 22:05
c16b58f to
dbb68f5
Compare
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.
Sets the version and dates the changelog section so
v0.8.0can be tagged.just check-version(whichrelease-builddepends on, and which the releaseworkflow runs first) rejects a tag that does not match
__version__, and alsorejects an undated
(unreleased)changelog heading — the changelog is part ofthe published description, so an undated heading would ship to PyPI as the
first thing on the page. Both now pass:
Published metadata on the built wheel:
This is what finally gets the #32 fix to consumers — PyPI still serves 0.7.1
pinned to
tldextract==2.2.2.After merging, tag to publish:
Does not include #45; that stays open by request.