release: v0.2.2 (PyPI publish retry of v0.2.1)

v0.2.1 shipped the container to GHCR and the GitHub Release but
publish-pypi failed with `invalid-publisher` — trusted-publishing
wasn't configured on pypi.org for this repo yet. That's now set up
(Owner=simtabi, Repository=shimkit, Workflow=release.yml,
Environment=pypi). v0.2.2 also carries the GHCR job's `contents:
write` grant (fdae429) so the container SBOM lands on the Release
page.

Code byte-identical to v0.2.1 and v0.2.0; bump is purely release
infra.

Author: imanimanyara

CHANGELOG.md

@@ -6,6 +6,21 @@ This project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.htm
 
 ## [Unreleased]
 
+## [0.2.2] — 2026-05-14
+
+### Fixed
+
+- Release pipeline: trusted-publishing now configured on PyPI for
+  this repo + workflow + `pypi` environment, so `publish-pypi` can
+  exchange its OIDC token for an upload credential. v0.2.1 published
+  the container to GHCR and the GitHub Release but failed at the
+  PyPI step with `invalid-publisher`. Also carries the release.yml
+  `contents: write` grant on the `publish-ghcr` job so the container
+  SBOM lands on the Release page instead of erroring with "Resource
+  not accessible by integration".
+- **Code is byte-identical to v0.2.1 (and v0.2.0); the bump is
+  purely a release-infra retry to land the artifact on PyPI.**
+
 ## [0.2.1] — 2026-05-14
 
 ### Fixed

pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "shimkit"
-version = "0.2.1"
+version = "0.2.2"
 description = "A toolkit of developer utilities — Java version manager, shell upgrader, and more. Python tools, shimmed by bash."
 readme = "README.md"
 license = { file = "LICENSE" }

src/shimkit/__init__.py

@@ -3,5 +3,5 @@
 Python tools, shimmed by bash.
 """
 
-__version__ = "0.2.1"
+__version__ = "0.2.2"
 __all__ = ["__version__"]