Repository navigation
release: prepare and publish Base v1.10.1 #2520
Description
Goal
Prepare and publish Base v1.10.1 through the governed cross-repository release train.
Scope
- prepare the release metadata and current-release documentation;
- validate the selected component tags and full commit pins;
- run the Ubuntu 24.04 and macOS 14 Ecosystem Release BOM workflow;
- run the guarded release check and preserve the BOM evidence;
- publish only after explicit maintainer approval, then verify the tag, assets, immutable readback, Homebrew handoff, and downstream documentation.
Release classification
This is a patch release containing release-process guardrails, CI/preflight tooling, and documentation alignment. Treat it as a high-impact patch for the release-artifact boundary: record the candidate window and independent review or solo-maintainer waiver before publication.
Acceptance criteria
- The v1.10.1 milestone has no unrelated open work at final preflight.
- The release-prep PR passes the full required hosted matrix.
- The BOM is generated at the exact merged Base commit and passes on Ubuntu 24.04 and macOS 14.
basectl release publish --dry-runpasses with the preserved BOM.- Publication is separately approved and followed by public release, checksum, package, documentation, and immutable-release readback.
Non-goals
Do not add the stable basectl release train command or the Base 1.11.0 AI-harness work; those remain tracked separately.
Metadata
Metadata
Assignees
Type
Projects
- Status
Activity
release: prepare Base v1.10.1 (#2521)
codeforester commentedon Oct 13, 2026
Candidate evidence recorded:
9bd1a5484ac10acda2c3a012ab89f7d9393e8d26.58521a0f467046859858dc3f9249e895f139aae2a1af7cf0593bc7ff710119b1basefoundry/basev1.10.1 to9bd1a5484ac10acda2c3a012ab89f7d9393e8d26, base-cli v0.5.1, base-bash-libs v2.2.2, and base-demo v0.2.1; required Ubuntu 24.04 and macOS 14 combinations passed.bin/base-release-bom validatepassed.bin/basectl release check --version 1.10.1 --bom ...passed with statusok.bin/basectl release publish --version 1.10.1 --bom ... --dry-runpassed.Publication, Homebrew handoff, and final public readback remain pending explicit maintainer approval.
codeforester commentedon Oct 13, 2026
Publication reached GitHub but is not complete.
v1.10.1exists and peels to reviewed commit9bd1a5484ac10acda2c3a012ab89f7d9393e8d26.Cannot upload assets to an immutable release.58521a0f467046859858dc3f9249e895f139aae2a1af7cf0593bc7ff710119b1.I am stopping before the Homebrew handoff. The release-publish implementation needs a recovery/design decision because immutable releases cannot accept assets after publication.
codeforester commentedon Oct 13, 2026
Follow-up fix is now in PR #2522. It changes
basectl release publishto passrelease-bom.jsonandrelease-bom.sha256directly togh release create, so GitHub uploads them before immutable publication. Local validation: 1793 Python tests and 1041 BATS tests passed; hosted checks are running.Homebrew report: the live
basefoundry/homebrew-basetap currently publishes Base1.9.0, and the inspected machine has Base1.9.0installed. Thereforebrew upgrade basefoundry/base/basecorrectly reports no upgrade.brew update basefoundry/base/baseis not a formula-refresh command; Homebrew rewrites it tobrew upgrade. The tap must receive a Base formula PR after a governed Base release before that command can upgrade.fix(release): attach BOM assets before immutable publish (#2523)
codeforester commentedon Oct 19, 2026
Superseded by the successful v1.10.5 release. The v1.10.1 publication exposed the immutable-release asset-ordering defect; PR #2523 fixed it, and v1.10.5 successfully published the BOM assets with cross-platform evidence and Homebrew handoff.