Skip to content

feat: adopt X-Client-Info attribution header and bump SDK floor to 3.1.2 - #15

Merged
tyler5673 merged 1 commit into
mainfrom
chore/sdk-3.1.2-attribution-header
Aug 21, 2026
Merged

feat: adopt X-Client-Info attribution header and bump SDK floor to 3.1.2#15
tyler5673 merged 1 commit into
mainfrom
chore/sdk-3.1.2-attribution-header

Conversation

@tyler5673

Copy link
Copy Markdown
Contributor

What this adds

Bumps the Python SDK floor from >=3.0.0,<4 to >=3.1.2,<4 and adopts the SDK's new X-Client-Info attribution header (shipped in youdotcom 3.1.2).

The plugin now passes app_name="youdotcom-temporal" and app_version=<package version> to the You(...) constructor instead of mutating client.sdk_configuration.user_agent post-construction. Each outbound request carries:

  • user-agent: youdotcom-python-sdk/3.1.2 httpx/<v> (SDK identity)
  • X-Client-Info: sdk; client=youdotcom-temporal/<version>; ua=python/<v> httpx/<v> (plugin identity)

The _USER_AGENT constant and the sdk_configuration.user_agent mutation are removed.

Changes

File Change
pyproject.toml youdotcom>=3.0.0,<4 -> >=3.1.2,<4
src/youdotcom_temporal/_client.py Pass app_name / app_version to You(...); drop _USER_AGENT and user_agent mutation
tests/test_client.py Assert app_name / app_version in constructor kwargs; drop _USER_AGENT assertions
CHANGELOG.md Unreleased entry
uv.lock Regenerated (3.0.0 -> 3.1.2)

Verification

  • uv run ruff check -- passed
  • uv run mypy src -- passed (0 issues)
  • uv run pytest -- 77 passed, 8 deselected (integration)

Related

  • Linear: DX-784
  • Stacked follow-up: DX-721 -- livecrawl to extraction migration (separate PR branched off this one)

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>

Replace the post-construction `user_agent` mutation with `app_name` /
`app_version` constructor kwargs so the SDK's `X-Client-Info` header
emits `client=youdotcom-temporal/<version>` on every outbound request.
The SDK's own `user-agent` stays as `youdotcom-python-sdk/<v>`.

- Bump `youdotcom>=3.0.0,<4` to `>=3.1.2,<4`
- Drop `_USER_AGENT` constant and `sdk_configuration.user_agent` mutation
- Update `tests/test_client.py` to assert the new constructor kwargs
- Regenerate `uv.lock`

Closes DX-784

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
@tyler5673
tyler5673 marked this pull request as ready for review August 21, 2026 19:21
@tyler5673
tyler5673 merged commit 000d54e into main Aug 21, 2026
5 of 7 checks passed
@tyler5673
tyler5673 deleted the chore/sdk-3.1.2-attribution-header branch August 21, 2026 20:42
tyler5673 added a commit that referenced this pull request Aug 21, 2026
Rebased onto main with PR #15 (SDK 3.1.2 + attribution header) and
PR #16 (extraction parameter) merged. Squashes the nexus spike into
one clean commit.

- YouDotComService exposes all six Activities as async Nexus Operations
- contract.py holds the Nexus contract with SDK response models
- workflows.py ships six thin backing Workflows with per-Activity ceilings
- Idempotency key support for deduplication of Nexus StartOperation retries
- Unit tests covering contract, handler, and sandbox registration
- Integration tests for live Nexus round-trip (gated behind -m integration)

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
tyler5673 added a commit that referenced this pull request Aug 21, 2026
Rebased onto main with PR #15 (SDK 3.1.2 + attribution header) and
PR #16 (extraction parameter) merged. Squashes the nexus spike into
one clean commit.

- YouDotComService exposes all six Activities as async Nexus Operations
- contract.py holds the Nexus contract with SDK response models
- workflows.py ships six thin backing Workflows with per-Activity ceilings
- Idempotency key support for deduplication of Nexus StartOperation retries
- Unit tests covering contract, handler, and sandbox registration
- Integration tests for live Nexus round-trip (gated behind -m integration)

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
tyler5673 added a commit that referenced this pull request Sep 3, 2026
* feat: add Nexus Service support (workflow-backed Operations)

Rebased onto main with PR #15 (SDK 3.1.2 + attribution header) and
PR #16 (extraction parameter) merged. Squashes the nexus spike into
one clean commit.

- YouDotComService exposes all six Activities as async Nexus Operations
- contract.py holds the Nexus contract with SDK response models
- workflows.py ships six thin backing Workflows with per-Activity ceilings
- Idempotency key support for deduplication of Nexus StartOperation retries
- Unit tests covering contract, handler, and sandbox registration
- Integration tests for live Nexus round-trip (gated behind -m integration)

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>

* fix: update stale DX-776 comments, fix annotated_types passthrough, correct timeout_s comment

- contract.py, nexus.py: SDK 3.1.2 shipped lazy imports (PEP 562), so the
  imports_passed_through() wrapper is belt-and-braces rather than load-bearing.
  Updated comments that referenced DX-776 as future work.
- workflows.py: comment claimed the Activity forwards timeout_s untouched
  but activities.py substitutes 120s when timeout_s is None, preventing the
  SDK effort-based deadline derivation. Corrected to describe actual behavior.
- plugin.py: re-added annotated_types to _PASSTHROUGH_MODULES, eliminating
  13 UserWarning messages about late import under the workflow sandbox.

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>

* fix: update workflows.py comment after PR #17 rebase

The Activity now forwards timeout_s as-is (PR #17 merged), so the SDK
derives the effort-based deadline itself. Updated the comment that
described the old 120s substitution behavior.

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>

* fix: contents Operation result model and research background guard

ContentsOutput wrapped the wrong SDK model: Contents (the search
extraction shape) instead of ContentsResponse (the contents endpoint
response), silently dropping url, title, and metadata from every
result element.

The research Operation accepted ResearchInput.background=True, but
with background=True the SDK returns a task handle that can never
validate as the Operation's ResearchResponse result. It now rejects
background=True with a non-retryable YouValidationError before any
billable call; research_background is the Operation for that mode.

Also restructures the CHANGELOG Unreleased section so it merges
cleanly against main's 1.1.0 release.

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>

---------

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant