Skip to content

docs: align release guidance with Base 1.10 - #336

Merged
codeforester merged 5 commits into
mainfrom
documentation/325-20261005-remove-stale-release-prose
Oct 6, 2026
Merged

codeforester merged 5 commits into
mainfrom
documentation/325-20261005-remove-stale-release-prose

Conversation

@codeforester

Copy link
Copy Markdown
Collaborator

Summary

Remove stale Base 1.8.0/demo 0.1.0 claims from the capability matrix and dependency-inputs guide. Clarify that the stable demo contract is Base 1.9.0/demo v0.2.0, while the exact Base v1.10.0 candidate lane is advisory until the release and final BOM are verified.

Issue

Fixes #325

Validation

  • python3 tests/validate_capability_matrix.py (11 rows; passed)
  • git diff --check
  • Hosted validation is required on the stacked candidate-pin base.

Notes

This PR is intentionally stacked on the candidate-pin PR #335. Historical release records, including docs/v0.2.0-readiness.md, remain unchanged.

@codeforester codeforester left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed head 2c3b624 against #325 (stacked on #335). No findings. The stale Base 1.8.0/demo 0.1.0 claims are gone. The matrix and dependency-inputs guide now state the stable 1.9.0/v0.2.0 contract and keep the v1.10.0 candidate lane explicitly advisory until the release and final BOM are verified, consistent with #335's pin. CI fails only on the undici audit (#334/#338). Ready after #338 and #335.

@codeforester
codeforester force-pushed the ci/324-20261005-refresh-v1-10-candidate-pin branch from 3d57f7b to 4dcd38b Compare October 6, 2026 02:33
@codeforester
codeforester force-pushed the documentation/325-20261005-remove-stale-release-prose branch from 2c3b624 to 43fe1cd Compare October 6, 2026 02:33
@codeforester
codeforester force-pushed the ci/324-20261005-refresh-v1-10-candidate-pin branch from 4dcd38b to ced333c Compare October 6, 2026 02:37
@codeforester
codeforester force-pushed the documentation/325-20261005-remove-stale-release-prose branch from 43fe1cd to 3ed37a6 Compare October 6, 2026 02:38
@codeforester
codeforester force-pushed the documentation/325-20261005-remove-stale-release-prose branch from 3ed37a6 to 52cd4d3 Compare October 6, 2026 12:54
Base automatically changed from ci/324-20261005-refresh-v1-10-candidate-pin to main October 6, 2026 13:18
@codeforester
codeforester merged commit db4ba8a into main Oct 6, 2026
8 checks passed
@codeforester
codeforester deleted the documentation/325-20261005-remove-stale-release-prose branch October 6, 2026 13:18
codeforester added a commit that referenced this pull request Oct 6, 2026
## Summary

Extend the advisory Base v1.10 workspace scenario with disposable Git
fixtures for the new `workspace update` safety contract. The scenario
now proves that dry-run JSON rejects dirty checkouts, manifest paths
nested inside an ancestor checkout, and clean default branches tracking
the wrong upstream branch, without changing the checkout. Update the
scenario guide and capability matrix to describe the coverage.

## Issue

Fixes #327

## Validation

- `python3 tests/scenarios/workspace.py --base
/private/tmp/base-candidate-06715 --base-commit
06715fed19aceff27844aba546ba2a0b4c594ac7 --base-cli
/private/tmp/base-cli-8a93 --bash-libs /private/tmp/base-bash-libs-36fec
--python /opt/homebrew/bin/python3 --candidate` (all scenario groups
passed)
- `python3 tests/scenario_harness_test.py` (2 passed)
- `python3 tests/validate_capability_matrix.py` (11 rows; passed)
- `git diff --check`
- Hosted `scenarios` workflow is required on the stacked train.

## Notes

This PR is stacked on documentation PR #336, which is stacked on
candidate-pin PR #335. The fixtures are temporary and local; no learner
checkout, trust store, or host workspace is modified.
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.

Remove stale pre-v0.2.0 Base 1.8.0/demo 0.1.0 prose from capability-matrix and dependency-inputs docs

1 participant