Prepare GixPython 0.2.0 for release

Prepare the next release without changing the existing `v0.1.0` tag so the
maintainer can tag the reviewed release commit. Align the Cargo manifest,
root lockfile package version, and Python runtime version assertion.

Finalize the dated changelog from changes since `v0.1.0`: native fixture
callbacks, upstream error propagation and removal of vendored crates,
developer recipes, and release CI placement. Remove the local-checkout
selector from the new feature list because it already shipped in `v0.1.0`.
Update installation and release guidance for `0.2.0`, and record preparation
status and local validation without claiming artifacts or publication.

Validation on Apple Silicon with ordinary CPython 3.14.7:

- Locked offline Cargo metadata and release metadata agree on `0.2.0`.
- All nine helper checks pass.
- Packaged extension builds offline with C/C++ compilers disabled.
- All 110 Python integration tests pass, with two expected skips, after
  allowing localhost access for disposable HTTP/TLS test servers.
- All seven Rust unit tests, Rust formatting, and whitespace checks pass.

Maturin is unavailable locally. Release-profile artifacts, Intel and
free-threaded validation, and final remote CI remain for the release workflow.
No tag, push, account interaction, or publication was performed.

Author: codex

CHANGELOG.md

@@ -7,21 +7,30 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## Unreleased
 
+## 0.2.0 (2026-10-14)
+
 ### New Features
 
  - Expose native cached read-only and writable fixtures through `gix.testtools`,
    with Python closures for fixture creation and post-processing.
- - Select a local Gitoxide checkout for Python development builds with
-   `GIXPYTHON_GITOXIDE_PATH` or `--gitoxide-path`, using a separate development
-   lockfile. `--packaged` forces release dependencies. Local builds report checkout HEAD.
+
+### Bug Fixes
+
+ - Propagate native errors from fallible path, configuration, reference,
+   shallow-state, and worktree queries after updating Gitoxide.
 
 ### Other
 
- - Use public Gitoxide `main` containing all three upstream prerequisites and
-   remove the vendored crates. `gix 0.89.0` does not yet include these fixes.
- - Reintegrate the updated Gitoxide `pygix` branch and its security-audit base.
-   Refresh the three bundled prerequisites and propagate native errors from
-   fallible path, configuration, reference, shallow-state, and worktree queries.
+ - Pin Gitoxide to public `main` revision
+   `09f85be4e3fda42f3e8fd19c53a63758fdf6fb3d`, containing the upstream prerequisites
+   for per-client TLS configuration, raw reflog messages, and literal submodule
+   names. Remove the vendored crates and packaged patches. `gix 0.89.0` does not
+   yet include these fixes.
+ - Group developer commands in the `justfile` and add `just run-release` for
+   isolated exploration of the latest or a specified published version, with
+   IPython completion for interactive sessions.
+ - Run platform-independent release validation and source archive creation on
+   Ubuntu, while retaining macOS builds and tests for all four release wheels.
 
 ## 0.1.0 (2026-10-05)
 

Cargo.lock

@@ -1,6 +1,6 @@
 [package]
 name = "pygix"
-version = "0.1.0"
+version = "0.2.0"
 edition = "2024"
 rust-version = "1.89"
 authors = ["Sebastian Thiel <sebastian.thiel@icloud.com>"]

Cargo.toml

@@ -39,7 +39,7 @@ Native iterators and output streams remain lazy. Use their context managers or `
 
 ## Installation
 
-Once version 0.1.0 is published, install it with:
+Install the latest published version with:
 
 ```sh
 python -m pip install --only-binary=:all: GixPython

README.md

@@ -1,6 +1,6 @@
 # Releasing GixPython
 
-The first version is **0.1.0**, for **macOS 11+ on Apple Silicon and Intel**.
+Version **0.2.0** targets **macOS 11+ on Apple Silicon and Intel**.
 The release contains four wheels and one source archive:
 
 | Architecture | Ordinary CPython | Free-threaded CPython |
@@ -14,8 +14,9 @@ Source builds require Rust 1.89+, a linker, and access to the pinned Rust depend
 
 ## One-time maintainer setup
 
-Use a PyPI account with two-factor authentication. Register a pending GitHub
-Trusted Publisher with these exact values:
+Use a PyPI account with two-factor authentication. For a first upload, register
+a pending GitHub Trusted Publisher with these exact values. For an existing
+project, confirm that its Trusted Publisher uses the same values:
 
 | Field | Value |
 | --- | --- |
@@ -43,6 +44,14 @@ Use Gitoxide's changelog style: `## VERSION (YYYY-MM-DD)`, with `New Features`,
 `Bug Fixes`, and `Other` sections when applicable. Set the date to the actual
 release day before creating the tag.
 
+For `0.2.0`, review the dated section in `CHANGELOG.md` and keep `Unreleased`
+for future changes. Validate locally before committing the preparation:
+
+```sh
+python3 etc/check_release.py --tag v0.2.0
+just helper-tests
+```
+
 Run CI on the final commit. Then start the **Release** workflow from that
 commit's branch with **publish unchecked**, or use:
 
@@ -64,14 +73,18 @@ older development artifacts separate from the release set.
 
 ## Publish
 
-After reviewing the tested commit, create an annotated tag `v0.1.0` and push
+After reviewing the tested commit, create an annotated tag `v0.2.0` and push
 that tag to `origin`. Start **Release** again with that tag selected and
 **publish checked**:
 
 ```sh
-gh workflow run release.yml --repo GitoxideLabs/GixPython --ref v0.1.0 -f publish=true
+git tag -a v0.2.0 -m "Release GixPython 0.2.0"
+git push origin v0.2.0
+gh workflow run release.yml --repo GitoxideLabs/GixPython --ref v0.2.0 -f publish=true
 ```
 
+Preserve the existing `v0.1.0` tag and published history.
+
 The workflow checks that the tag matches the version, rebuilds and tests the
 complete set, then waits for the `pypi` environment approval. Approve the job
 after inspecting its artifacts. The official PyPI action uploads those exact
@@ -82,11 +95,12 @@ Once uploaded, verify on both architectures and both interpreter kinds:
 
 ```sh
 python -m venv .release-check
-.release-check/bin/python -m pip install --only-binary=:all: GixPython==0.1.0
+.release-check/bin/python -m pip install --only-binary=:all: GixPython==0.2.0
 .release-check/bin/python -c 'import gix; print(gix.__version__, gix.build_features())'
 ```
 
 For free-threaded Python, set `PYTHON_GIL=0` and verify importing `gix` leaves
-`sys._is_gil_enabled()` false. An optional GitHub release can use the version's
-changelog text. PyPI filenames cannot be replaced after upload; corrections
-require a new version.
+`sys._is_gil_enabled()` false. The workflow publishes to PyPI only; create an
+optional GitHub release separately for `v0.2.0`, using only the `0.2.0` section
+of `CHANGELOG.md` as its release notes. PyPI filenames cannot be replaced after
+upload; corrections require a new version.

RELEASING.md

@@ -102,3 +102,11 @@ configuration destruction/retry while an in-memory native owner is active
 (`e33597f`). The [validation record](validation.md) lists the passing release
 wheel, free-threaded, hash-selection, Rust, and no-C builds, and distinguishes
 local evidence from platform checks configured for CI.
+
+## Release preparation
+
+Version `0.2.0` is prepared locally with aligned Cargo metadata and Python
+version checks, dated release notes, and updated maintainer instructions.
+Local validation is recorded in [validation.md](validation.md). The maintainer
+will create the tag; final platform CI, release artifact validation, and
+publication remain separate steps in [RELEASING.md](../RELEASING.md).

docs/implementation-plan.md

@@ -1,5 +1,26 @@
 # Local validation
 
+## Version 0.2.0 preparation (2026-10-14)
+
+The Cargo manifest, root lockfile package, locked offline Cargo metadata,
+and Python package version assertion agree on `0.2.0`. The release metadata
+gate accepts `v0.2.0`; all nine build/release/justfile helper checks pass.
+The dated changelog consolidates changes since `v0.1.0`, and the maintainer
+instructions use the new version while preserving the existing tag.
+
+The packaged extension builds offline on Apple Silicon with C/C++ compilers
+disabled. CPython 3.14.7 passes all 110 integration tests with two expected
+skips. The initial sandboxed run could not bind loopback HTTP/TLS servers;
+the full suite passes when localhost access is allowed. All seven Rust unit
+tests, Rust formatting, and whitespace checks pass. The runtime reports
+`0.2.0` and the packaged Gitoxide revision
+`09f85be4e3fda42f3e8fd19c53a63758fdf6fb3d`.
+
+No `0.2.0` release artifacts, free-threaded or Intel builds, remote CI, tag,
+push, or publication were performed. Maturin is unavailable locally; the
+manual Release workflow remains responsible for building and validating
+the complete four-wheel and source-archive set before publication.
+
 ## Python fixture tools (2026-10-12)
 
 The pinned `gix-testtools 0.22.0` is available as `gix.testtools` in default

docs/validation.md

@@ -11,7 +11,7 @@ def test_import_keeps_the_gil_disabled(self):
         self.assertFalse(sys._is_gil_enabled())
 
     def test_build_identity(self):
-        self.assertEqual(gix.__version__, "0.1.0")
+        self.assertEqual(gix.__version__, "0.2.0")
         self.assertIn("parallel", gix.build_features())
         self.assertTrue({"sha1", "sha256"}.intersection(gix.build_features()))
         self.assertEqual(len(gix.__gix_revision__), 40)