release 0.1.3

dynamic-config-python-remote/CHANGELOG.md

@@ -30,6 +30,20 @@ is the door into this one.
 
 ## [Unreleased]
 
+## 0.1.3 — 2026-08-16
+
+### Changed
+
+- **Moved with the base wheel** to
+  [dynamic-config-rs/dynamic-config-python](https://github.com/dynamic-config-rs/dynamic-config-python).
+  `dynamic-config-py[remote]` still resolves to this pair, and the pair
+  still versions together.
+
+- **The project links and the classifiers**, as in the base wheel:
+  `Documentation` points at the remote-wheel chapter of the Python book,
+  `Issues` was added, and the store names are keywords so a search for
+  `etcd` or `vault` finds this at all.
+
 ## 0.1.2 — 2026-08-14
 
 ### Changed

dynamic-config-python-remote/Cargo.toml

@@ -9,7 +9,7 @@ name = "dynamic-config-python-remote"
 # release that moves the base wheel and not this one is fine (the extra keeps
 # working); the reverse is not, which is why the compatibility floor is
 # declared in `pyproject.toml` rather than assumed.
-version = "0.1.2"
+version = "0.1.3"
 edition.workspace = true
 # The highest floor of anything linked in, measured rather than declared:
 # PyO3, etcd and `gix` ask for 1.85, and `aws-sdk-sts`, `async-nats` and

dynamic-config-python-remote/pyproject.toml

@@ -55,7 +55,7 @@ classifiers = [
 # remote path at all. It is not `==` for the reason the Rust crates are: a
 # wheel that pinned its sibling exactly would make every base-wheel patch a
 # forced upgrade of this one.
-dependencies = ["dynamic-config-py>=0.1.2"]
+dependencies = ["dynamic-config-py>=0.1.3"]
 dynamic = ["version"]
 
 [project.urls]

dynamic-config-python/CHANGELOG.md

@@ -26,6 +26,32 @@ breaking.
 
 ## [Unreleased]
 
+## 0.1.3 — 2026-08-16
+
+### Changed
+
+- **The wheels moved to their own repository**,
+  [dynamic-config-rs/dynamic-config-python](https://github.com/dynamic-config-rs/dynamic-config-python),
+  and release on their own schedule from there. The package name, the
+  import name and the API are unchanged; what moved is where issues are
+  filed and where the book lives —
+  [dynamic-config-rs.github.io/python/](https://dynamic-config-rs.github.io/python/).
+
+- **The project links on PyPI say more.** `Homepage` is the book rather
+  than a Rust workspace's front page, `Documentation` points at the API
+  reference, and `Issues` was added — a reader arriving from PyPI now
+  lands on Python prose in one click.
+
+- **More keywords and classifiers**, because both are how PyPI's search
+  and filters find a package at all: `Framework :: Pydantic`,
+  `Framework :: AsyncIO`, the systems-administration and distributed
+  topics, and the words a person actually types (`dotenv`, `toml`,
+  `twelve-factor`, `live-reload`).
+
+- **The engine and the store crates are named with a caret** in the
+  manifests these wheels are built from, so a patch release of either
+  reaches a source build without a release here.
+
 ## 0.1.2 — 2026-08-14
 
 ### Added

dynamic-config-python/Cargo.toml

@@ -13,7 +13,7 @@ name = "dynamic-config-python"
 # So this moves when *this* changes — a new Python API, a behaviour
 # change, or an engine bump worth shipping — and `maturin upload
 # --skip-existing` makes a release that changed nothing here a no-op.
-version = "0.1.2"
+version = "0.1.3"
 edition.workspace = true
 # Its own floor, not the workspace's 1.71: PyO3 needs more than the core does.
 rust-version = "1.85"