release: pyproc-worker 0.1.1 (PyPI)

[YuminosukeSato]

pyproc-worker 0.1.1 Release

Release Python package to PyPI with observability support.

Changes

• Version: 0.1.0 → 0.1.1
• New Feature: W3C Trace Context extraction (tracing.py)
• Compatible with: pyproc v0.7.1 Go package

What's New

W3C Trace Context Support

# Automatically extracts trace context from Go requests
from pyproc_worker.tracing import extract_trace_context

# Works with OpenTelemetry (optional dependency)
pip install pyproc-worker[telemetry]

Optional Dependencies

• orjson (required): High-performance JSON codec
• opentelemetry-api, opentelemetry-sdk (optional): Tracing support
• msgspec (optional): MessagePack codec

Backward Compatibility

✅ No breaking changes

• Existing code works without modification
• Tracing module works without OpenTelemetry installed (graceful degradation)

Testing

• All existing tests pass
• New tracing tests added

PyPI Release

After merge, publish to PyPI:

cd worker/python
uv build
uv publish

Co-Authored-By: Claude Sonnet 4.5 noreply@anthropic.com

[Copilot]

Pull request overview

Releases pyproc-worker v0.1.1 to PyPI, aligning the package metadata with the new release.

Changes:

• Bumped Python package version from 0.1.0 to 0.1.1.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ae6d9aa972

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Keep telemetry version aligned with release version

Updating project.version to 0.1.1 without updating the hardcoded service.version in pyproc_worker/tracing.py causes all traces from this release to still report 0.1.0. In environments that use version tags for rollout monitoring or regression triage, this mislabels production telemetry and makes it difficult to attribute issues to the actual deployed package version.

Useful? React with 👍 / 👎.