Repository navigation
ci: publish the first immutable demo release after readiness gates #28
Description
Activity
- added a commit that references this issue
on Sep 19, 2026 - added a commit that references this issue
on Oct 8, 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.
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
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.
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.
Metadata
Metadata
Assignees
Type
Projects
- Status
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
Related work
Continuation after #16, whose scope explicitly excluded publishing. This issue does not authorize publication by itself.
Project fields