release 0.1.1

[vgreg]

Prepares the 0.1.1 release. No functional changes beyond what is already on main; this only cuts the changelog section and bumps the version.

Changes

• CHANGELOG.md: the two [Unreleased] entries move under ## [0.1.1] - 2026-08-22, with compare links updated so [Unreleased] now points at v0.1.1...HEAD.
• Version bumped 0.1.0 → 0.1.1 via bump-my-version, which updated pyproject.toml, src/iolaus/__init__.py, and its own current_version. This is the first bump since the drift fix landed, and it correctly touched all three locations.

What 0.1.1 ships

Both fixes are already merged on main:

• --set overrides are parsed as TOML, so values keep their types instead of arriving as strings
• Quick-start examples corrected so the documented invocations actually run

The override fix is a behaviour change (--set model__lr=0.01 previously yielded '0.01', now 0.01), but it is the documented and intended behaviour, and 0.1.0 has been on PyPI for roughly an hour, so patch is the right level.

Tagging

I deliberately ran the bump with --no-tag. Tagging on this branch would put v0.1.1 on a commit that is not on main's first-parent line. Once this merges I will tag the merge commit on main and push, which triggers the publish workflow and parks it for your approval in the release environment.

Verification

• 17 tests pass; ruff check and mypy --strict clean
• uv build produces iolaus-0.1.1 sdist and wheel, both pass twine check
• import iolaus; iolaus.__version__ reports 0.1.1
• mkdocs build --strict clean

🤖 Generated with Claude Code

[vgreg]

Amended to fix something gh caught on push: uv.lock records the project's own version and was left at 0.1.0 by the bump, since bump-my-version only knows about the files listed in its config.

The stale lock is now folded into the bump commit, and I wired a hook so this cannot recur:

pre_commit_hooks = ["uv lock", "git add uv.lock"]

I chose a hook over a fourth [[tool.bumpversion.files]] entry deliberately: a plain search/replace for version = "0.1.0" inside uv.lock would also rewrite any dependency that happens to sit at the same version. Regenerating the lock is exact.

Verified by running a throwaway bump patch to 0.1.2 and inspecting the resulting commit:

 pyproject.toml         | 4 ++--
 src/iolaus/__init__.py | 2 +-
 uv.lock                | 2 +-

All three files picked up automatically. Rolled that back, so the branch is still at 0.1.1.

Branch was force-pushed (--force-with-lease) to amend the lock into the bump commit rather than leave a stale-then-fixed pair in history.