Milestones
List view
Backward-compatible release-process hardening and the first dogfood train for the new cross-repository release controls. This milestone must be empty of open release issues before publication.
No due date•5/5 issues closedThis release is focussed on guardrails, governance, and AI skills.
Due by November 7, 2026•1/11 issues closedNative Windows Phase 1 support: platform adapters, PowerShell launcher, read-only command subset, and release evidence.
No due date•0/4 issues closedStabilization and adoption-readiness release following v1.9.0. 165 of 167 tracked issues are closed; the remaining two (#2291, #2482) are the final release-gate checks — validating the updated Base Demo and adopting base-bash-libs v2.2.2 — before v1.10.0 ships. Delivered so far: - Release & ecosystem BOM integrity: governed, schema-validated release-BOM path with a canonical digest and sidecar single-sourcing (#2170-2173, #2208, #2254, #2397), a hardened and retry-safe Ecosystem Release BOM workflow with centralized test fixtures (#2174, #2189, #2207, #2209, #2220), component release-tag verification before BOM attestation (#2417), and semver-policy-compatible downstream version-bump automation (#2119, #2263, #2289, #2484). - Workspace lifecycle & safety: `basectl workspace test`, workspace doctor, and onboarding action sequences (#2101, #2104, #2106); safer workspace update that rejects ancestor checkouts, mismatched upstream branches, and empty/dirty/non-tracking manifests (#2336, #2341-2343); a versioned, published workspace-status JSON contract (#2467-2468); and a verified, full `basectl uninstall` (#2110, #2395, #2418, #2428). - CLI/dispatch correctness: consistent handling of a bare `help` token and projects literally named "help" across every subcommand (#2350, #2388, #2429, #2457), fixes to config-flag passthrough, clean-wrapper arithmetic flags, process-tree termination on timeout, and GitHub Project/issue-readiness lookups (#2247, #2249, #2415, #2438, #2470-2472). - Security & trust: installer checksum verification, full-history trust revocation, a `--test-requirements-sha256` guard, and consistent subprocess-output redaction across workspace test/setup reports and read boundaries (#2188, #2222-2223, #2349, #2396, #2402, #2424-2425, #2453). - Internal consolidation: a large dedup pass sharing Python setup, project-interpreter probes, history/table-width rendering, GitHub Project transport-error handling, PR-template defaults, and shell-prompt/profile-diagnostic helpers across commands (#2297-2309, #2325-2326); `repo.sh` and `setup_common.sh` split by ownership boundary (#2117, #2354-2355, #2357-2358); and dogfooding base-bash-libs in place of divergent shell reimplementations (#2122). - Documentation & positioning: the v1.9.0 and v1.10.0 CHANGELOG entries (#2166, #2416), a rewritten README/STANDARDS positioning hero with `build` added to the command list (#2338-2339, #2363, #2381-2382), an ecosystem map and support matrix (#2118, #2264), and reconciled docs for WSL2/Windows, workspace update, and the test-requirements trust guard (#2346, #2401-2402). - Community & governance: the adopter golden-path and release-stabilization/review policy (#1619-1620), co-maintainer onboarding and bus-factor mitigation planning (#2108), an organization-wide OSS health baseline with triage/starter-issue/response-cadence processes (#2265, #2267-2268), and three good-first-issue docs tasks for new adopters (#2278-2280). - CI hardening: build-target and Python-interpreter policy test coverage (#2145-2146), workflow-contract tests split under the Pylint module limit (#2212), ShellCheck extended to Base-managed shell startup files (#2436), Core product validation promoted to an enforced merge gate (#2452), and the Base Demo E2E workflow repaired and exercising Go/live-HTTP contracts (#2290, #2458).
No due date•165/167 issues closedIdeas for future, to be taken up for implementation only if there is a significant demand.
No due date•0/18 issues closed