@@ -5,9 +5,26 @@ All notable changes to Cellucid will be documented here.
 The format is based on [Keep a Changelog](https://keepachangelog.com/),
 and this project adheres to [Semantic Versioning](https://semver.org/).
 
-## [0.9.1]
+## [0.9.2]
 <!-- CELLUCID_VERSION -->
 
+Version 0.9.2 is a patch release on 0.9.1.
+
+### Fixed
+
+- A refused upload or event now reaches the client as the status the server sent.
+  Every early refusal of a POST -- an expired or unknown session-bundle request, bad
+  viewer credentials, a wrong `Content-Type`, an oversized body, an unknown path, a
+  foreign `Host` -- was answered before the request body was read, and the socket
+  was then closed with that body unread. A socket closed with unread input is reset
+  rather than shut down, so a client still sending or not yet reading lost the
+  response: Windows reported `WinError 10053`, macOS and Linux a reset or a broken
+  pipe. The server now drains a refused request's declared body, within the
+  largest accepted upload and for at most five seconds, before it closes. Both
+  servers share one `do_POST` that does this.
+
+## [0.9.1] - 2026-10-17
+
 Version 0.9.1 is the PyPI submission release.
 
 ### Added
@@ -211,6 +228,7 @@ declared `0.0.9`. Release 0.9.1 restores one exact version across both systems.
   - Jupyter integration (`show()`, `show_anndata()`)
 - Export functionality for web deployment
 
+[0.9.2]: https://github.com/theislab/cellucid-python/releases/tag/v0.9.2
 [0.9.1]: https://github.com/theislab/cellucid-python/releases/tag/v0.9.1
 [0.0.9]: https://github.com/theislab/cellucid-python/releases/tag/v0.9.0
 [0.0.1a0]: https://github.com/theislab/cellucid-python/releases/tag/v0.0.1a0
@@ -2,7 +2,7 @@ cff-version: 1.2.0
 message: "If you use this software, please cite it."
 type: software
 title: "cellucid (Python): Interactive Single-Cell Data Visualization"
-version: 0.9.1  # CELLUCID_VERSION
+version: 0.9.2  # CELLUCID_VERSION
 authors:
   - family-names: Inecik
     given-names: Kemal
 
@@ -22,7 +22,7 @@
 
     release = version = __version__
 except Exception:
-    release = version = "0.9.1"  # CELLUCID_VERSION
+    release = version = "0.9.2"  # CELLUCID_VERSION
 
 # -- General configuration ---------------------------------------------------
 extensions = [
 
@@ -248,7 +248,7 @@ It provides:
 
 The reader validates this object against an exact key set, so a key that is not
 listed here makes the dataset fail to load. In this example
-`cellucid_data_version` is `0.9.1`. <!-- CELLUCID_VERSION -->
+`cellucid_data_version` is `0.9.2`. <!-- CELLUCID_VERSION -->
 
 ```json
 {
@@ -257,7 +257,7 @@ listed here makes the dataset fail to load. In this example
   "name": "PBMC demo",
   "description": "",
   "created_at": "2026-01-01T00:00:00Z",
-  "cellucid_data_version": "0.9.1",
+  "cellucid_data_version": "0.9.2",
   "stats": {
     "n_cells": 10000,
     "n_genes": 2000,
 
@@ -18,7 +18,7 @@ Key sections:
 
 - `[project]`
   - `name = "cellucid"`
-  - `version = "0.9.1"` (beta) <!-- CELLUCID_VERSION -->
+  - `version = "0.9.2"` (beta) <!-- CELLUCID_VERSION -->
   - runtime dependencies (`numpy`, `pandas`, `scipy`, `anndata`, `ipython`, `jupyter-server-proxy`)
 - `[project.optional-dependencies]`
   - `dev`: `pytest`, `ruff`, `mypy`, `pre-commit`
 
@@ -6,10 +6,10 @@ the release candidate is reviewed and publication is explicitly authorized.
 
 ## Versioning policy
 
-`cellucid` is currently in beta (`0.9.1`). <!-- CELLUCID_VERSION -->
+`cellucid` is currently in beta (`0.9.2`). <!-- CELLUCID_VERSION -->
 
 - Package versions use three numeric components.
-- Git tags use the exact package version with a `v` prefix, such as `v0.9.1`. <!-- CELLUCID_VERSION -->
+- Git tags use the exact package version with a `v` prefix, such as `v0.9.2`. <!-- CELLUCID_VERSION -->
 - PyPI distributions, citation metadata, documentation, and the downstream
   recipe declare the same version.
 - The normalized source distribution has one reproducible byte stream, and its
@@ -73,13 +73,13 @@ Run the repository validator after all release metadata except the source
 digest is aligned:
 
 ```bash
-python scripts/validate_release.py --tag v0.9.1
+python scripts/validate_release.py --tag v0.9.2
 ```
 
 The command must finish with:
 
 ```text
-Cellucid Python release contract is valid for v0.9.1.
+Cellucid Python release contract is valid for v0.9.2.
 ```
 
 ### 2. Run source and documentation gates
@@ -103,7 +103,7 @@ python -m pip install "build==1.5.0" "twine==6.2.0"
 SOURCE_DATE_EPOCH=315532800 python -m build
 python scripts/normalize_sdist.py dist
 python -c "import hashlib, pathlib; p=next(pathlib.Path('dist').glob('cellucid-*.tar.gz')); print(hashlib.sha256(p.read_bytes()).hexdigest())"
-python scripts/validate_release.py --tag v0.9.1 --sdist dist
+python scripts/validate_release.py --tag v0.9.2 --sdist dist
 python -m twine check --strict dist/*
 ```
 
@@ -128,7 +128,7 @@ For each artifact, verify:
 
 ```bash
 python -m pip check
-python -c "import cellucid; assert cellucid.__version__ == '0.9.1'"
+python -c "import cellucid; assert cellucid.__version__ == '0.9.2'"
 cellucid --version
 cellucid --help
 cellucid serve --help
@@ -151,13 +151,13 @@ Commit and push the reviewed source first. Wait for branch CI and docs checks to
 finish successfully. Then create and push the exact annotated tag:
 
 ```bash
-git tag -a v0.9.1 -m "Cellucid Python 0.9.1"
-git push origin v0.9.1
+git tag -a v0.9.2 -m "Cellucid Python 0.9.2"
+git push origin v0.9.2
 ```
 
 The `Publish to PyPI` workflow:
 
-1. checks out complete Git history, validates `v0.9.1`, and requires the tagged <!-- CELLUCID_VERSION -->
+1. checks out complete Git history, validates `v0.9.2`, and requires the tagged <!-- CELLUCID_VERSION -->
    `GITHUB_SHA` to be an ancestor of the fetched `origin/main`;
 2. runs Ruff, mypy, the complete pytest suite, and a strict documentation build;
 3. builds one wheel and one source distribution;
@@ -178,9 +178,9 @@ After the workflow succeeds, create a clean environment and install from PyPI:
 python -m venv cellucid-release-check
 source cellucid-release-check/bin/activate
 python -m pip install --upgrade pip
-python -m pip install "cellucid==0.9.1"
+python -m pip install "cellucid==0.9.2"
 python -m pip check
-python -c "import cellucid; assert cellucid.__version__ == '0.9.1'"
+python -c "import cellucid; assert cellucid.__version__ == '0.9.2'"
 cellucid --version
 ```
 
 
@@ -4,11 +4,12 @@ This guide documents the **`cellucid` Python package**: how to prepare datasets,
 
 If you’re looking for the end-user web UI docs (loading data, filtering, analysis, annotation), start with {doc}`../web_app/index`.
 
-:::{admonition} Active package version — 0.9.1
+:::{admonition} Active package version — 0.9.2
 :class: note
+<!-- CELLUCID_VERSION -->
 
-Version **0.9.1** is the current Cellucid Python source and documentation
-version and the PyPI submission release. The
+Version **0.9.2** is the current Cellucid Python source and documentation <!-- CELLUCID_VERSION -->
+version and the current PyPI release. The
 [PyPI package page](https://pypi.org/project/cellucid/) is authoritative for
 registry availability. Check an installed environment with
 `python -c "import cellucid; print(cellucid.__version__)"`; the
 
@@ -5,12 +5,12 @@
 **Goal:** install `cellucid`, verify the CLI, and avoid the most common environment pitfalls
 
 :::{note}
-**Active package version: 0.9.1.** Version 0.9.1 is the PyPI submission
+**Active package version: 0.9.2.** Version 0.9.2 is the current PyPI <!-- CELLUCID_VERSION -->
 release. If the [PyPI package page](https://pypi.org/project/cellucid/) lists
-0.9.1, the normal install and pin commands below retrieve it. Until then, they <!-- CELLUCID_VERSION -->
+0.9.2, the normal install and pin commands below retrieve it. Until then, they <!-- CELLUCID_VERSION -->
 resolve only to versions available from PyPI; install the active source
 straight from the official GitHub repository (see **From the official source
-repository** below) when validating 0.9.1 before publication. <!-- CELLUCID_VERSION -->
+repository** below) when validating 0.9.2 before publication. <!-- CELLUCID_VERSION -->
 :::
 
 ## Requirements
@@ -120,7 +120,7 @@ pip install -U cellucid
 Pin a specific version (recommended for paper pipelines):
 
 ```bash
-pip install "cellucid==0.9.1"  # CELLUCID_VERSION
+pip install "cellucid==0.9.2"  # CELLUCID_VERSION
 ```
 
 ### Core scientific runtime
 
@@ -10,10 +10,11 @@ If you want notebook embedding, servers, and programmatic control, see the {doc}
 For the web UI experience after export (loading, filtering, analysis, sessions, community annotation), see {doc}`../web_app/index`.
 ```
 
-:::{admonition} Active package version — 0.9.1
+:::{admonition} Active package version — 0.9.2
 :class: note
+<!-- CELLUCID_VERSION -->
 
-Version **0.9.1** is the active Cellucid for R source and documentation
+Version **0.9.2** is the active Cellucid for R source and documentation
 version and the CRAN submission release. The
 [CRAN package index](https://cran.r-project.org/web/packages/available_packages_by_name.html)
 is authoritative for registry availability. Check an installed environment
@@ -41,7 +42,7 @@ matching CRAN and official-source installation paths.
 :link: installation
 :link-type: doc
 
-Install version 0.9.1 from the source currently available to you, verify the <!-- CELLUCID_VERSION -->
+Install version 0.9.2 from the source currently available to you, verify the <!-- CELLUCID_VERSION -->
 loaded package, and diagnose dependency or environment problems.
 :::
 
 
@@ -2,15 +2,15 @@
 
 **Audience:** everyone  
 **Time:** 5–15 minutes (depending on your setup)  
-**Goal:** install Cellucid for R, verify version 0.9.1, and choose the correct <!-- CELLUCID_VERSION -->
+**Goal:** install Cellucid for R, verify version 0.9.2, and choose the correct <!-- CELLUCID_VERSION -->
 source for current registry availability
 
 :::{note}
-**Active package version: 0.9.1.** Version 0.9.1 is the CRAN submission
+**Active package version: 0.9.2.** Version 0.9.2 is the CRAN submission
 release. The
 [CRAN package index](https://cran.r-project.org/web/packages/available_packages_by_name.html)
 is authoritative for registry availability. Use the CRAN command below when
-the index lists `cellucid` 0.9.1; otherwise install the active source from the
+the index lists `cellucid` 0.9.2; otherwise install the active source from the
 official GitHub repository.
 :::
 
@@ -29,16 +29,16 @@ Those packages are only needed if you want to follow the Seurat/SCE recipes in t
 
 ## Install Cellucid
 
-### From CRAN when version 0.9.1 is listed
+### From CRAN when version 0.9.2 is listed
 <!-- CELLUCID_VERSION -->
 
-When the CRAN package index lists `cellucid` 0.9.1, install it with: <!-- CELLUCID_VERSION -->
+When the CRAN package index lists `cellucid` 0.9.2, install it with: <!-- CELLUCID_VERSION -->
 
 ```r
 install.packages("cellucid")
 ```
 
-If the index does not list version 0.9.1 yet, use the official source <!-- CELLUCID_VERSION -->
+If the index does not list version 0.9.2 yet, use the official source <!-- CELLUCID_VERSION -->
 installation below.
 
 ### From the official source repository
@@ -70,7 +70,7 @@ packageVersion("cellucid")
 
 You should see:
 - No error on `library(cellucid)`
-- Version `0.9.1` from `packageVersion` <!-- CELLUCID_VERSION -->
+- Version `0.9.2` from `packageVersion` <!-- CELLUCID_VERSION -->
 
 ## Optional dependencies (recommended)