Skip to content

[v1.0] Define dependency compatibility windows and a tested version matrix #189

Description

@codeforester

Goal

Turn dependency compatibility into an explicit, tested, and supportable release contract.

Background

The framework accepts broad dependency ranges without publishing tested lower/upper windows, leaving resolver outcomes and breakage risk unclear.

Scope

Inventory direct and transitive runtime dependencies; choose supported lower and upper bounds; add a CI matrix for minimum/latest supported and relevant Python versions; define an upper-bound update and security-exception policy; publish the support table.

Acceptance Criteria

  • Every runtime dependency has a reasoned window.
  • CI covers minima and latest supported versions.
  • Unsupported combinations fail clearly.
  • Docs match pyproject metadata and release automation.
  • Upgrades have a repeatable review path.

Validation

Run the full test/lint/type-check matrix; build/install the wheel under minimum and latest environments; verify the support table.

Non-Goals

Do not solve the YAML optional-dependency split here; that is tracked separately.

Project Fields

  • Status: Backlog
  • Priority: P1
  • Area: Packaging
  • Initiative: v1.0 Readiness
  • Size: M

Ownership

Metadata

Metadata

Assignees

Labels

ciContinuous integration, tests, automation, or release workflows

Type

No type

Projects

Status
Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions