v1.0.1

What's Changed

• chore(identity): adopt the Kontur repository mark by @NikAcc in #25
• docs: align overview and release status by @NikAcc in #26
• chore: finalize dependency and CI hygiene by @NikAcc in #27
• chore: enforce one weekly dependency PR by @NikAcc in #28
• fix(renovate): enforce one weekly update group by @NikAcc in #29

Full Changelog: v1.0.0...v1.0.1

v1.0.0

What's Changed

• chore(deps): bump the uv-compatible group across 1 directory with 3 updates by @dependabot[bot] in #18
• chore(deps): bump ruff from 0.16.0 to 0.16.1 in the uv-compatible group by @dependabot[bot] in #21
• feat!: align CLI and supported-runtime contracts by @NikAcc in #22

Full Changelog: v0.2.1...v1.0.0

v0.2.1

What's Changed

• docs: record v0.2.0 channels and deduplicate CI by @NikAcc in #13
• ci: record each release channel as a deployment by @NikAcc in #14
• chore: enable native dependency updates by @NikAcc in #15
• chore(deps): bump actions/checkout from 5 to 7 by @dependabot[bot] in #16
• chore: preserve post-merge workflow triggers by @NikAcc in #19
• chore(deps): bump python-semantic-release/python-semantic-release from 9 to 10 by @dependabot[bot] in #17
• fix: scope isolated GitHub release publishing by @NikAcc in #20

New Contributors

• @dependabot[bot] made their first contribution in #16

Full Changelog: v0.2.0...v0.2.1

v0.2.0

What's Changed

• feat: harden export confinement, concurrency, scale, and progress by @NikAcc in #12

Full Changelog: v0.1.1...v0.2.0

v0.1.1

What's Changed

• fix: refresh uv.lock during release so its version cannot lag by @NikAcc in #10
• fix: treat both lock identities as sources, and check the tagged lock by @NikAcc in #11

Full Changelog: v0.1.0...v0.1.1

v0.1.0

What's Changed

• feat: add durable manifests, run history, and scale budgets by @NikAcc in #9

Full Changelog: v0.0.4...v0.1.0

v0.0.4

What's Changed

• Show progress, and stop a truncated manifest line from poisoning resume by @NikAcc in #5
• Modernize Immich Export maintenance by @NikAcc in #6
• Harden Immich export integrity by @NikAcc in #7
• fix: make release cleanup checkout-safe by @NikAcc in #8

Full Changelog: v0.0.3...v0.0.4

v0.0.3

v0.0.3 (2026-07-13)

This release is published under the MIT License.

Bug Fixes

• release: Attach the sdist and wheel to the GitHub Release (#4, 34bb701)

The semantic-release action only runs 'version' — it bumps, tags, writes the changelog and creates the GitHub Release, but it never runs 'publish'. So every Release was created with no files attached: a bare tag pointing at PyPI.

Upload the sdist and wheel that semantic-release already built, so the Release stands on its own. That matters for a tool whose whole purpose is to be an escape hatch — you should be able to grab it from GitHub without going through a package index.

Uses the preinstalled gh CLI rather than another action, so the org's Actions allow-list does not need a new entry.

---

Detailed Changes: v0.0.2...v0.0.3

v0.0.2

v0.0.2 (2026-07-13)

This release is published under the MIT License.

Bug Fixes

• release: Drop the duplicate build that broke publishing (#3, 2f8683b)

The release job died at 'Build sdist + wheel' with

PermissionError: [Errno 13] Permission denied: dist/-0.0.1.tar.gz

python-semantic-release already builds the sdist and wheel into dist/ via the build_command in pyproject.toml. It is a Docker action running as root, so those artefacts are root-owned. The workflow then ran a second, redundant 'uv build' as the unprivileged runner user, which cannot overwrite them.

Publish to PyPI and the Homebrew bump are both gated on that step, so a permission error on a build that never needed to happen silently took out the entire release.

Remove the duplicate build and the setup-uv step that only served it, and let the publish action consume the dist/ that semantic-release produced.

---

Detailed Changes: v0.0.1...v0.0.2