Skip to content

feat: validate independent downstream consumers - #99

Merged
codeforester merged 1 commit into
mainfrom
enhancement/72-20260805-validate-production-consumers
Aug 5, 2026
Merged

codeforester merged 1 commit into
mainfrom
enhancement/72-20260805-validate-production-consumers

Conversation

@codeforester

Copy link
Copy Markdown
Contributor

Summary

  • publish an adopter readiness checklist, migration path, support channel, and friction/release disposition register
  • add three independent downstream compatibility fixtures: Atlas (Click), Beacon (Typer), and Cinder (automation/JSON)
  • retain per-consumer packaging, documentation, tests, and a wheel-first compatibility workflow
  • validate the consumer manifest and include downstream evidence in source distributions and repository documentation

Validation

  • python3 scripts/validate_consumers.py
  • python3 scripts/validate_examples.py
  • python3 scripts/validate_docs.py
  • .venv/bin/python -m pytest -q
  • all three downstream consumer suites via PYTHONPATH=lib/python:compatibility/consumers/<consumer>/src
  • ruff check and ruff format --check
  • ./tests/validate.sh

Closes #72

@codeforester
codeforester marked this pull request as ready for review August 5, 2026 16:48
@codeforester
codeforester merged commit 0203347 into main Aug 5, 2026
49 of 50 checks passed
@codeforester
codeforester deleted the enhancement/72-20260805-validate-production-consumers branch August 5, 2026 16:49
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.

Validate base-cli with three independent production consumers

1 participant