Release 0.2.1: the README in plain English - #15
Merged
Merged
Conversation
PyPI shows the README as the package's description, and it only changes when a version is uploaded, so the rewrite in #14 is not what a PyPI reader sees until a release carries it. This bumps the version in pyproject.toml and both lock files, and moves the Unreleased notes under 0.2.1. There is no code, contract or spec/ change.
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.
PyPI shows the README as the package's description, and that page only changes when a version is uploaded. The rewrite in #14 does not reach PyPI until a release carries it.
This is a documentation-only release:
versiongoes to0.2.1inpyproject.toml,uv.lockandexamples/otlp/uv.lock.Unreleasednotes move under0.2.1 — 2026-09-22inCHANGELOG.md.There is no code, contract or
spec/change. After merge,v0.2.1is tagged on the merge commit and the release workflow publishes it through trusted publishing.