Repository navigation
ci: publish the first immutable demo release after readiness gates #28
Description
Problem
The v0.1.0 preparation is complete, but the repository has no GitHub release. Newcomers currently have a moving checkout rather than a tagged reference with immutable artifacts and a known framework floor. Publishing should follow the new correctness and version-identity gates.
Verified evidence
Reviewed on 2026-09-12 at 2de6b83f21ccacae04f8050f5691d0dd8159fda1; the local checkout matches GitHub main.
On 2026-09-12 the GitHub releases endpoint returns an empty list. VERSION, package metadata and the README target 0.1.0. Closed #16 explicitly prepared the release without publishing, and .github/workflows/release-package.yml validates/uploads workflow artifacts without creating a GitHub Release.
Sources:
Acceptance criteria
- After first-release defects and version-identity checks are resolved, prepare a concrete release plan and complete the separately authorized publication step.
- Publish an immutable tag/release with tested source/wheel artifacts and checksums plus exact supported base-cli version evidence.
- Provide a stable install/checkout path in the README and verify it in a clean environment.
- Do not imply that demo 0.1.0 freezes the framework API or requires a framework release.
Related work
Continuation after #16, whose scope explicitly excluded publishing. This issue does not authorize publication by itself.
Project fields
- Status: Backlog
- Priority: P2
- Area: Packaging
- Initiative: Base-CLI Demo
- Size: S
- Assignee: @codeforester
- Milestone: v0.1.0
- Target date: unscheduled
Metadata
Metadata
Assignees
Type
Projects
- Status
Activity
ci: attach verified release artifacts after authorization (#40)
docs: remove unpublished demo wheel instructions (#52)
codeforester commentedon Oct 9, 2026
Release preflight on main 9f245af: basectl release check/plan/notes/publish --dry-run passed; ./tests/validate.sh passed (70 tests); ./tests/package.sh built and twine-validated the 0.1.0 sdist and wheel; hosted Tests and Compatibility are green. Publication is still paused while #23 restores authenticated Project Intake and #27 completes end-to-end required-check verification. No tag or GitHub Release has been created yet.
codeforester commentedon Oct 9, 2026
Draft v0.1.0 release prepared and verified. Tag v0.1.0 points to main commit 9f245af. Asset workflow 37918349459 passed all four compatibility jobs on Python 3.10 and 3.13 against published base-cli 0.4.3. Draft assets attached: base_cli_demo-0.1.0-py3-none-any.whl, base_cli_demo-0.1.0.tar.gz, COMPATIBILITY.txt, and SHA256SUMS.txt; downloaded checksum verification passed for all four assets. Draft release: https://github.com/basefoundry/base-cli-demo/releases/tag/untagged-e41af8cfccfe94c1155f
codeforester commentedon Oct 9, 2026
v0.1.0 is now publicly published at https://github.com/basefoundry/base-cli-demo/releases/tag/v0.1.0. Public assets are present and SHA256SUMS.txt verifies the wheel, sdist, COMPATIBILITY.txt, and checksum file. Remaining release-contract gap: GitHub API reports immutable-releases enabled=false and the published release immutable=false. #28 and milestone v0.1.0 remain open until release immutability is enabled and the treatment of this already-published release is decided.
codeforester commentedon Oct 10, 2026
Completed by the already-published v0.1.0 GitHub Release. The release assets and checksums are available at https://github.com/basefoundry/base-cli-demo/releases/tag/v0.1.0; subsequent v0.2.0 preparation is tracked in #55.