Markdown docs and source views got richer (
de53757, dd8d24e, 92fea07)
The API now returns rendered HTML for markdown files in the source view, and the frontend can toggle between Preview and Code. File views also link import/export specifiers, and package Docs pages now show a chip with the number of documented symbols so API surface size is visible at a glance.
Usage snippets and create commands became more accurate (63cf7f4, 16f738e)
Docs now advertise deno create for packages that export ./create, and usage snippets are version-aware: pinned versions stay pinned, while latest versions use a caret-constrained specifier. That makes the generated copy-paste instructions line up better with what Deno actually installs and lints.
Support mail handling was fixed end-to-end (ab690dc, 38f0785, 871ff49, 9b9a9f9, 4f1807c)
Inbound mail now uses the forwarder’s SPF/DKIM result instead of Postmark’s, the API can enqueue email deliveries again, and staff can reply to unclaimed email tickets without 500s. The ticket system also gained staff-only internal notes, canned replies, and a better post-login redirect back to the ticket being claimed.
Other misc changes
- Markdown heading permalink icons now survive sanitization; footnotes and their wrapper markup do too, and anchor links keep the right styling (2923b8c, 56cbf83).
- Added syntax highlighting for TOML, YAML, C, and extra filename aliases in code blocks (ccd90c7).
- Packages with browser/workerd-only support now show npm-ecosystem usage instructions again (bad5fe4).
- Module JSDoc examples now render on the package overview even when README is the prose source (d547043).
- Symbol listings now show
@deprecatedtext when there’s no other documentation (60f1fb8).