Skip to content

docs: record 0.1.1 release evidence - #28

Merged
tensornull merged 1 commit into
mainfrom
docs/record-0.1.1-release
Jul 29, 2026
Merged

docs: record 0.1.1 release evidence#28
tensornull merged 1 commit into
mainfrom
docs/record-0.1.1-release

Conversation

@tensornull

Copy link
Copy Markdown
Contributor

Summary

  • mark cometapi==0.1.1 as publicly available
  • record the exact fix, release-PR, immutable tag, live-smoke, OIDC, digest, provenance, and public-registry evidence
  • record the accepted maintenance release in the repository's canonical architecture and agent contract
  • preserve the completed 0.1.0 and Registry Alpha evidence as historical records

Why

The normal v0.1.1 Release Please/OIDC workflow and independent public-PyPI verification are complete. Repository documentation must now describe shipped behavior and retain the final remote, live, and registry evidence in a separate post-release change.

Impact

Documentation only. This change does not alter package code, workflow code, version metadata, release variables, tags, releases, or registry state. It does not activate 0.2.

Verification

  • uv sync --locked
  • uv lock --check
  • Ruff check and format check
  • Pyright strict
  • pytest -m "not live" (308 passed, 1 deselected)
  • version/changelog and public-document checks
  • secret and workflow semantic checks
  • actionlint 1.7.12
  • final standalone copied-checkout verification, including build, twine, artifact inspection, wheel/sdist clean installs, and all README examples
  • git diff --check
  • independent Standards and Spec review

No required local check was skipped. The separately gated exact-release live and public-registry checks are linked in the recorded release evidence and were not rerun for this documentation-only PR.

@tensornull
tensornull merged commit e07b4e7 into main Jul 29, 2026
10 checks passed
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.

1 participant