[dmccoystephenson]

The version in pyproject.toml and trace_client/trace_client.py is set to 0.4.2 for the stable release.

Opened by release automation. Nothing is published by this PR: once it is merged, the merge commit is run through the library's own tests, a save-compatibility check against 0.4.1 and every consumer's test suite, and only a commit that passes is tagged 0.4.2. See python-release-gates.

---

drafted by Claude on behalf of Daniel Stephenson

[dmccoystephenson]

Review of the 0.4.2 release PR (head of release/0.4.2-a69dc64). It has the same two problems as #25, so it is left open for the owner. Version bumps and pyproject.toml changes are owner-only release decisions.

This PR duplicates #25. gh pr diff 25 and gh pr diff 27 are byte-for-byte identical: the same two one-line changes to pyproject.toml and trace_client/trace_client.py, both on top of main at a69dc64. The release automation seems to have opened a second release PR instead of reusing the first. Only one of the two should be kept. Neither is closed here, because the release automation may track its branches by name.

1. The version bump is incomplete, so the test suite fails on this PR's head. Only 2 of the 5 places that hold the version string were bumped:

• pyproject.toml:7: 0.4.2
• trace_client/trace_client.py:22 (__version__): 0.4.2
• trace_client/trace_client.py:1: the module header still says trace-client 0.4.1
• trace_client/__init__.py:1: the module header still says trace-client 0.4.1
• tests/test_trace_client.py:296 and :301: test_user_agent_names_the_client_version still expects 0.4.1

Running python3 -m unittest on this head with Python 3.8.10 locally gives Ran 67 tests ... FAILED (failures=2). Both failures come from that test (AssertionError: '0.4.1' != '0.4.2').

2. CI cannot pass right now, for reasons that have nothing to do with this diff. Run 40807343754 failed at test (3.8) with The version '3.8' with architecture 'x64' was not found for Ubuntu 26.04, and fail-fast then cancelled 3.10 and 3.12. This is tracked in #26. Every PR is blocked until the owner picks one of the workflow fixes listed there.

Rubric:

• Scope: PASS. Only the two files that hold the version are touched.
• Version agreement: FAIL. 3 of the 5 places still say 0.4.1.
• Tests: FAIL. 2 local failures on this head, both from the test assertions that were not bumped.
• CI: FAIL. It is red because of the runner image, so it says nothing about this diff (CI: test (3.8) can no longer install Python 3.8 on ubuntu-latest (Ubuntu 26.04), so every Build run fails #26).
• Stdlib-only / never-raises / log level / exports: PASS. No code changed.
• Java parity: no change a Java user would see, apart from the version in the User-Agent.
• Do-not-auto-merge: this PR changes pyproject.toml and the version string, so the owner has to merge it.

Suggested order for the owner: fix #26 first, then keep one of #25/#27, add the three missing version bumps to it, and close the other.

#16 was also skipped this cycle. A release PR is already open, and the fix changes which tags are sent on the wire, so the owner needs to decide it together with trace-client-java.

This review was drafted during a Gardener session (https://github.com/Stephenson-Software/gardener).

---

drafted by Claude on behalf of Daniel Stephenson