[taskmedia-bot]

🤖 I have created a release beep boop

1.0.0 (2026-11-03)

Features

• add a copy-permalink button and pinned heading links to the docs (#99) (541e9f2)
• add a settings registry and generate the settings reference (#120) (#126) (cdef257)
• build older docs versions from git tags instead of committed snapshots (#84) (aca0080)
• default the letter subject to the page title unless subject is explicitly empty (#90) (f672f82)
• edge-proxy recipes (nginx, Caddy, Traefik) to load the PDF action without the injector (#108) (d9f8e62)
• hide the metadata block in outline's reading view (#89) (b737ef3)
• load the pdf action through a mounted outline page template (#110) (8404d96)
• send the button options with the status and document the script tag contract (#112) (c84ab2c)
• show a .pdf file-type hint on the PDF item in the Export menu (#88) (819b06e)

Bug Fixes

• copy the docs snapshot into versioned_docs/version-X.Y (#81) (eb6537b)
• make the documentation screenshots reproducible (#91) (4da32fd)
• publish the outprint image and let release-please pick the next version (#109) (e4f1e17)
• render diagrams under reduced motion, add traefik on kubernetes tab (#133) (e995079)

---

This PR was generated with Release Please. See documentation.

[fty4]

Do not merge this yet. Two problems:

1. The `outprint` image was never published for v0.1.0. The `publish outprint` job of the v0.1.0 release (run 41344384894) failed at the multi-arch manifest step (`ghcr.io/taskmedia/outprint@sha256:08660dbc…: not found`). Cause: the job downloads artifacts with `digests-outprint-`, which also matches `digests-outprint-injector-`, so it tries to merge injector digests into the `outprint` repository. `outprint-injector` publishes fine because its pattern is unambiguous. Result: `ghcr.io/taskmedia/outprint:0.1.0` and `:latest` do not exist, which also fails `ct install` in feat(outprint): add Helm chart helm#26.
2. This PR targets 0.1.0 again (`compare/v0.1.0...v0.1.0`) because `release-as: "0.1.0"` is still set in `release-please-config.json`. With it removed and `bump-minor-pre-major: true`, the `feat:` commits since v0.1.0 give 0.2.0.

Plan: fix the artifact name pattern in `release-please.yml`, drop `release-as`, then let release-please re-open this as 0.2.0.

[taskmedia-bot]

🤖 Created releases:

• v1.0.0

🌻