Release python 1.0.2: sentinel-based update() so callers can clear nullable fields

links.update() and bundles.update() previously used None as both the
default and the explicit-null signal for label, expires_at, description,
and icon. A caller omitting label produced the same wire payload as one
passing label=None, so fields could not be cleared without always
sending them.

Optional nullable params now default to an UNSET sentinel; only keys
explicitly provided by the caller appear in the request body. Passing
None sends the field as JSON null, clearing it on the server. Sync and
async resources updated; regression tests added for both clients.

Author: DennisAlund

sdk/python/CHANGELOG.md

@@ -2,6 +2,10 @@
 
 All notable changes to the SDK are documented in this file.
 
+## 1.0.2 (2026-05-07)
+
+- `links.update()` and `bundles.update()` can now distinguish "omit this field" from "set this field to null". Optional nullable params (`label`, `expires_at`, `description`, `icon`) default to a private `UNSET` sentinel; only keys explicitly provided by the caller are included in the request body. Pass `None` to clear a value, omit the param to leave the server-side value untouched. Sync and async resources both updated; regression tests cover both clients.
+
 ## 1.0.1 (2026-04-30)
 
 Packaging, documentation, and CI hygiene. No public surface changes.

sdk/python/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "shrtnr"
-version = "1.0.1"
+version = "1.0.2"
 description = "SDK for the shrtnr URL shortener API"
 readme = "README.md"
 license = "Apache-2.0"