Merge pull request #17 from taskbadger/docs/external-id-v2.3.0

Document external_id and v2.2.0/v2.3.0 changelog

Author: snopoke

docs/changelog.md

@@ -5,6 +5,25 @@ hide:
 
 # Changelog
 
+Full release notes for the Python SDK are available on [GitHub](https://github.com/taskbadger/taskbadger-python/releases).
+
+## v2.3.0
+
+**2026-07-23**
+
+**Python SDK**
+
+* **NEW** The Celery and Procrastinate integrations now automatically record the originating task/job ID on the task [`external_id`](data_model.md#external_id) field.
+
+## v2.2.0
+
+**2026-07-09**
+
+**Python SDK**
+
+* **DEPRECATED** Per-task actions are deprecated.
+* **HOUSEKEEPING** Fix flaky Celery retry test.
+
 ## v2.1.0
 
 **2026-07-08**

docs/python-celery.md

@@ -218,6 +218,12 @@ Task Badger will create task records for each inner invocation with metadata sim
 }
 ```
 
+## External ID
+
+The Celery task ID is automatically recorded on the Task Badger task's
+[`external_id`](data_model.md#external_id) field, letting you correlate the Task Badger task with the
+originating Celery task.
+
 ## Opting out
 
 If you want to prevent TaskBadger from tracking a particular execution, set the `taskbadger_track` header (False) when publishing:

docs/python-procrastinate.md

@@ -154,6 +154,12 @@ Task Badger task, so you can monitor the history and health of your scheduled jo
 The name of the Procrastinate queue a task is deferred to is automatically recorded on the Task Badger
 task's [`queue`](data_model.md#queue) field.
 
+## External ID
+
+The Procrastinate job ID is automatically recorded on the Task Badger task's
+[`external_id`](data_model.md#external_id) field, letting you correlate the Task Badger task with the
+originating Procrastinate job.
+
 ## Known Limitations
 
 Procrastinate has no signals or middleware system, so the integration works by wrapping the task