Skip to content

feat(chat-with-content): add tested helpers and dedicated CI - #446

Open
amylin1249 wants to merge 9 commits into
mainfrom
cwc-01-helpers-and-ci
Open

feat(chat-with-content): add tested helpers and dedicated CI#446
amylin1249 wants to merge 9 commits into
mainfrom
cwc-01-helpers-and-ci

Conversation

@amylin1249

@amylin1249 amylin1249 commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

Split out of #433 into small, reviewable PRs (tracking issue #429). Stacked 1/3 — reviewable individually, merge bottom-up.

Pulls the unit-testable logic out of app.py into helpers.py, adds a test suite, and gives the extension its own CI workflow. No behavior change to the app in this slice; extension.version stays 0.0.7 (only the top of the stack bumps it).

Also aligns the toolchain:

  • .python-version pins the interpreter for local runs. uv was resolving Python 3.10 locally while CI pinned 3.12 and Connect deploys 3.12.7, so the suite ran on a different interpreter than either. The workflow already solved this for CI; this does it for contributors. The file was gitignored here, unlike the other extensions that carry one, so that entry is removed too.
  • astral-sh/setup-uv was four majors behind (v5) and out of step with the sibling workflows; now pinned to v9.0.0.

@github-actions

Copy link
Copy Markdown
Contributor

Extension release summary

😴 Changed but won't release

The following extensions have code changes but the manifest version hasn't been incremented:

  • chat-with-content: manifest version 0.0.7 ≤ released version 0.0.7
  • package-vulnerability-scanner: manifest version 3.0.6 ≤ released version 3.0.6
  • publisher-command-center: manifest version 0.0.8 ≤ released version 0.0.8
  • runtime-version-scanner: manifest version 1.0.5 ≤ released version 1.0.5
  • usage-metrics-dashboard: manifest version 1.0.15 ≤ released version 1.0.15

If you intended to release these changes, update the version field in each extension's manifest.json.

See the contributing guide for details.

… viewers

resolve_visitor_client returned the raw exception text for display when the
session token exchange failed. A viewer can't act on SDK/vendor error detail,
so log it server-side instead and show only the self-contained detail string.
…ings

The session-exchange-timeout message was hand-written inline in app.py with
different wording from NO_SESSION_DETAIL and EXCHANGE_FAILED_DETAIL, even
though it's the same category of failure (can't read the viewer's session).
Define it next to the other two so all three stay consistent.
@amylin1249
amylin1249 marked this pull request as ready for review July 29, 2026 17:39
@amylin1249
amylin1249 requested a review from dotNomad July 29, 2026 19:27
uv resolved Python 3.10 locally while CI pinned 3.12 and Connect deploys
3.12.7, so contributors ran the suite on a different interpreter than either.
The workflow already solved this for CI; .python-version does it for local runs,
matching how the other extensions carry it (it was gitignored here).

setup-uv was four majors behind and out of step with the sibling workflows.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.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