Repository navigation
Align the reference consumer with base-cli 0.5.0 #47
Description
Problem
base-cli-demo still targets the released 0.4.x framework line (base-cli>=0.4.3,<0.5) in its package metadata, lockfile, documentation, and compatibility/release workflows. The merged base-cli main branch now carries the 0.5.0 release candidate.
A candidate-wheel validation also found one consumer contract assertion that is stale for 0.5.0: a successful OpenTelemetry lifecycle span now reports status=OK rather than status=UNSET.
Scope
- move the declared and locked framework line to
base-cli>=0.5.0,<0.6once 0.5.0 is published; - update compatibility and immutable-release evidence workflows to exercise the 0.5.x line;
- update README and consumer documentation to describe the 0.5.0 boundary and migration expectations;
- update the telemetry consumer assertion and add a regression check against the 0.5.0 candidate;
- retain the existing explicit source-checkout policy; do not make the demo silently prefer a sibling checkout;
- keep the issue open until base-cli 0.5.0 is published and the demo package/release evidence is green.
Evidence
base-cli-demomain currently pinsbase-cli>=0.4.3,<0.5and resolvesbase-cli==0.4.3inuv.lock.- PyPI currently publishes base-cli 0.4.3; 0.5.0 is merged on base-cli main but not yet published.
- Against a locally built base-cli 0.5.0 candidate, the demo suite passes except the telemetry status assertion described above.
Refs basefoundry/base-cli#423.
Metadata
Metadata
Assignees
Type
Projects
- Status
Activity
codeforester commentedon Oct 5, 2026
Implementation is prepared in draft PR #48. The branch updates package metadata and lock resolution to
base-cli>=0.5.0,<0.6, compatibility/release workflows, docs, changelog, and the successful telemetry span assertion (status=OK). Local validation against a wheel built from base-cli main passed (65 tests, package validation,uv lock --check). The remaining prerequisite is publication of immutablebase-cli==0.5.0to PyPI; after that, refresh the lockfile against the published artifact, rerun hosted compatibility checks, and promote #48 from draft.codeforester commentedon Oct 7, 2026
Verification and inventory for the 0.5.0 release, from a review on 2026-10-07 against base-cli main
31d00f7b(VERSION 0.5.0, not yet on PyPI).Candidate run: in a clean venv with base-cli installed from main and all extras, 64 of 65 tests passed. The one failure is the telemetry assertion already described here (
status=UNSET, nowstatus=OK). The framework'sdocs/integrations.mddocumentsOKas the intended behavior, so the test is stale, not the framework. There are no other regressions.Locations to update when the line moves to 0.5 (all say
0.4.3/<0.5):pyproject.toml(dependency and theyamlextra),uv.lockREADME.md:50,README.md:145docs/compatibility.md(range, floor, "<0.5keeps the demo on 0.4", the==0.4.4rc1example)docs/should-i-use-base-cli.md:5-7,:51-52("newest published release is 0.4.3", "<0.5bound")docs/use-in-your-project.md:10.github/workflows/compatibility.yml(matrix==0.4.3/>=0.4.3,<0.5,0.4.4rc1example).github/workflows/published-release-assets.yml(matrix names/specs and the "Declared Base-CLI range" text at line 123)tests/test_optional_scenarios.py:117Also decide the new floor: if it moves to
0.5.0, the "minimum floor" job becomes==0.5.0.The framework side is tracked in basefoundry/base-cli#434 (checklist step to validate and bump the demo).
codeforester commentedon Oct 10, 2026
Completed by merged PR #48. The consumer now targets the published base-cli 0.5.0 line, has an exact public uv.lock resolution, and all hosted compatibility/consumer gates pass.