chore: release 0.2.1 - #8
Merged
Merged
Conversation
Bump the version in pyproject.toml and __init__.py, and add the 0.2.1 section to the CHANGELOG: the slash-only fqdn fix and create_domain().
Matches the convention of the 0.2.0 section, which opens on the issue it addresses.
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.
Release preparation for 0.2.1, a patch on top of #7.
versionbumped inpyproject.tomland__version__insrc/clever_cloud/__init__.py— the two are not derived from one another.CHANGELOG.mdgains the 0.2.1 section, keeping the existing headings: Fixed (a slash-onlyfqdnno longer yieldsDomain(domain="")) and Added (create_domain()).No code change in this PR.
Checks
Per
RELEASING.mdstep 2, all green:ruff check .mypy(strict, 13 source files)pytest --cov— 242 tests, 96% total coverageuv run --python 3.11 --extra dev --isolated pytest— 242 tests, against the oldest supported versionOnce this lands, the tag goes on the merge commit (
git tag -a v0.2.1), then build, verify, and publish.