Things I fixed in other people's code.

Routing handed the POST to the sibling endpoint and stopped there. Now an endpoint exporting neither POST nor fallback is treated as unusable and the request falls through to the page actions, mirroring the endpoint_can_handle pattern already used for GET/HEAD.

The page lacked link: true in its frontmatter, which is what makes the docs renderer emit the block controls and heading anchors. One line, and the reference page behaves like the rest of the documentation again.

The callable is handed the field name and its info object, which ConfigDict.field_title_generator already described correctly. This aligns the fields.py docstrings on Field(), FieldInfo.from_field(), computed_field() and ComputedFieldInfo with the signature the code actually calls.

A recent switch to secrets.compare_digest() broke it: the function only accepts ASCII when handed str. Encoding both sides to bytes first restores equality for any value and keeps the constant-time guarantee that motivated the switch.

group_path=True already collapsed these to the route template /users/{user_id}, but the safe behaviour was opt-in, so every default deployment leaked memory silently. I flipped the default and kept raw paths reachable through group_path=False.

The splitter broke before every capital letter, including each one inside an uppercase run. Splitting only at real word boundaries keeps acronyms intact: HTTPTimeoutError → HTTP Timeout Error, MissingJWTError → Missing JWT Error.

The relative Installation.md reference does not resolve in the built site, so it points at the full dj-stripe.dev installation URL instead. Jerome Leclanche, who maintains dj-stripe, merged it the same morning.