🚀 Release v0.1.1

[ubmarco]

Release 0.1.1

Version bump 0.1.0 → 0.1.1 plus changelog stamp. No library code changes — this is release-prep only.

Changes

• pyproject.toml + src/sphinx_mounts/__init__.py: version 0.1.0 → 0.1.1
• uv.lock: own-package version synced to 0.1.1
• docs/source/changelog.rst: the accumulated Unreleased entries are stamped as the 0.1.1 release (dated 2026-06-14), matching the 0.1.0 block's format (label + :Released:), with no empty Unreleased section left behind — same convention the 0.1.0 tag used.

Included in 0.1.1

• Per-mount path_check option ("error" default / "warn" / "off") that confines mounted-bundle directives to the bundle root (✨ NEW: enforce mounted-directive path confinement (path_check) #7)
• Regression coverage proving absolute diagnostic locations for mounted docs (🧪 TEST: prove absolute diagnostic locations for mounted docs #9)
• Regression coverage proving incremental rebuilds re-read mounted docs when their files / include targets change (🧪 TEST: re-read mounted docs when their files/include targets change #10)
• Sphinx 8 CI coverage — the matrix now exercises Sphinx 8 on Python 3.12 (full 7/8/9 coverage) (🧪 TEST: cover Sphinx 8 on py312 in the CI pytest matrix #11)

Intentionally excluded from the changelog

• ✨ NEW: reference a pre-built HTML report from a mounted bundle (html_extra_path) #6 (html_extra_path example) — the commit itself notes this is stock Sphinx composing with mounts, not a sphinx-mounts feature; only tests/example/ + tests/ changed, no src/.
• 🐛 FIX: wire Bazel doc-build targets into CI (and fix their missing extensions) #8 — CI-only (Bazel doc-build wiring).
• 📚 Add GitHub repo link to docs sidebar #4 — docs-site sidebar link (cosmetic).

Verification

• uv run prek run — all hooks pass (the CI Prek gate)
• uvx ruff@0.12.2 format --check — already formatted (CI's pinned ruff)
• sphinx-build -nW --keep-going — docs build succeeds; changelog renders

After merge

Publishing is tag-driven (PyPI Trusted Publishing via release.yaml). To cut the release:

git tag -a 0.1.1 -m "Release 0.1.1"
git push origin 0.1.1

The bare-semver tag (0.1.1, no v) matches the workflow trigger and publishes to PyPI.