Skip to content

Test manifests for every content Python uv provides #946

Closed

Description

@tdstein

🤖 ## Parent

#944

What to build

A test array proving that the CLI can write a correct manifest for every content Python that uv can provide (3.8 → current), whichever CLI Python runs it. For each version: locate the interpreter, create a virtual environment for it with one installed package and a minimal API project, run rsconnect write-manifest api <dir> --python <interpreter>, and check the output. The list of versions comes from what uv can provide, so new Pythons join automatically. Versions that aren't available locally are skipped.

Add a dedicated CI job that runs the array with a 3.11 CLI Python, installs every content Python through uv, and turns skips into failures. This works on today's codebase and lands before the 3.11 floor as the safety net for it. No bundle building: bundling runs entirely under the CLI Python.

Acceptance criteria

  • For each content Python, the manifest records that content Python's version (not the CLI Python's), package_manager is set, and requirements.txt contains the pinned package
  • Unavailable versions skip locally
  • A CI job with a 3.11 CLI Python installs all content Pythons and fails if any case is skipped
  • The array passes on the current codebase

Metadata

Metadata

Assignees

Labels

ready-for-agentFully specified, ready for an autonomous coding agent

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions