Skip to content

v0.11.0.md

Latest commit

 

History

History
61 lines (44 loc) · 1.85 KB

v0.11.0.md

File metadata and controls

61 lines (44 loc) · 1.85 KB

shimkit 0.11.0

Doc consolidation + PyPI workflow restoration. No source code changes. For the full machine-readable changelog, see CHANGELOG.md.

TL;DR

Three deliverables:

  1. Per-version release notes for v0.5.0 through v0.10.0 (docs/release-notes/v0.{5,6,7,7.1,8,9,10}.0.md). Previously only v0.2.0 had one. v0.7.1 is a thin stub pointing at v0.7.0.
  2. PyPI publish job restored in release.yml after sitting deferred since the v0.5.0 invalid-publisher incident. Uses pypa/gh-action-pypi-publish with OIDC trusted publishing. Runs in parallel with github-release after build.
  3. Architecture docs refreshed. docs/architecture.md lists the core/ and tools/ additions from v0.5-v0.11 (docker, host_service, version + eight new tools); added an "Adding a new tool" guidance block.

PyPI side

release.yml now has a publish-pypi job that runs in parallel with github-release after build. First PyPI upload is blocked on the user-side trusted-publisher setup:

Step Action
1 Log into PyPI → https://pypi.org/manage/account/publishing/ → add a pending publisher: Project Name=shimkit, Owner=simtabi, Repository=shimkit, Workflow=release.yml, Environment=pypi
2 GitHub: Settings → Environments → New environment named pypi. No secrets required.

Until both are done, the publish-pypi job fails with invalid-publisher but the github-release job still succeeds. Past tags (v0.11.0, v0.12.0+) can be re-uploaded retroactively via Actions → failed run → "Re-run failed jobs" once the config is in place.

Stats

  • Tests: unchanged (1027 passing as of v0.10.0)
  • Source LOC changes: 0
  • New files: 7 release-notes docs

Upgrading

uv tool upgrade shimkit
pipx upgrade shimkit

No behavioural changes.