chore(release): 0.4.0 - #44
Merged
Merged
Conversation
Minor rather than patch: #41 relaxed the OpenTelemetry constraints from exact pins to ranges, which changes what consumers can resolve. The distro can now be co-installed with other OpenTelemetry-based libraries that require a newer core (langfuse v3 and similar), so this is a consumer-visible capability change, not a bug fix. Add a 0.4.0 changelog entry covering everything since 0.3.0. Earlier releases (0.2.0, 0.3.0b0, 0.3.0) shipped without entries and are not backfilled here. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Greptile SummaryThe release metadata is updated for version 0.4.0.
Confidence Score: 5/5The PR appears safe to merge. No blocking failure remains.
|
| Filename | Overview |
|---|---|
| pyproject.toml | Bumps the package version to 0.4.0 so the release can be published under a new PyPI version. |
| CHANGELOG.md | Documents the 0.4.0 release and previously omitted HyperDX release history. |
Reviews (2): Last reviewed commit: "docs(changelog): backfill entries for 0...." | Re-trigger Greptile
|
Placeholder — see review field. |
Replace the placeholder note with real entries reconstructed from git history for the five HyperDX releases that shipped unlogged: 0.0.5, 0.1.0, 0.2.0, 0.3.0b0, and 0.3.0. Each entry records the OpenTelemetry package bump for that release, the Python version floor changes (3.7 dropped in 0.2.0, 3.8 dropped in 0.3.0b0), and the notable maintenance work, with PR references where they exist. Entries are ordered by release date. This surfaces a discontinuity that was previously hidden: the pre-existing entries (0.2.1b0 and older) come from the upstream Honeycomb distro this project was derived from and use that lineage's version numbers, so 0.2.1b0 is dated May 2023 while the HyperDX 0.0.5 release is September 2023. A separator marks the boundary rather than interleaving two numbering schemes. HyperDX 0.0.1 through 0.0.4 remain unrecorded. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
wrn14897
approved these changes
Jul 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
2 participants
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.
Bumping to 0.4.0 unblocks PyPI publishing. After #43 the Release job actually runs, but it now fails at the upload step with
400 File already existsbecause 0.3.0 is already on PyPI; merging this publishes 0.4.0 automatically.Minor rather than patch: #41 relaxed the OpenTelemetry constraints from exact pins to ranges, so the distro can be co-installed with other OpenTelemetry-based libraries that require a newer core.
This also backfills the changelog, which had recorded nothing since 2023. Entries for 0.0.5, 0.1.0, 0.2.0, 0.3.0b0 and 0.3.0 are reconstructed from git history (OpenTelemetry bumps, the Python 3.7 and 3.8 drops, notable maintenance), and a separator marks where the older Honeycomb-lineage entries begin, since those use a different numbering scheme and are why 0.2.1b0 is dated earlier than 0.0.5. HyperDX 0.0.1 through 0.0.4 remain unrecorded.