Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,4 +43,4 @@ Release publishing is tag-driven: create a matching `vX.Y.Z` git tag and push it
- `@mozilla/readability@0.6.0` was already the latest npm release at the time of the uplift. Do not upgrade it casually.
- Only widen sanitize-html or Readability/linkedom behavior with a clear reason and tests.
- Keep the container on Node 24.
- linkedom 0.18.x and sanitize-html 2.17.x are the supported parser and sanitizer pins; sanitize-html upstream is archived, do not expect backports.
- Do not hold linkedom or sanitize-html at a fixed supported version; take the latest compatible release. A caret range on a `0.x` package still pins its minor (`^0.18.13` keeps linkedom on 0.18), so bump that line by hand. The standalone sanitize-html repository is archived, so expect no backports and track new releases from the apostrophe monorepo.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,8 +18,8 @@ Markdown output is more portable and easier to consume in many contexts, but any
- Runtime: Node.js 24
- Package manager: npm
- Web framework: Express 5
- HTML parsing: linkedom 0.18
- Sanitization: sanitize-html 2.17
- HTML parsing: linkedom
- Sanitization: sanitize-html
- Deployment image: `node:24-alpine`

The container runs as a non-root user and the service exposes `POST /` plus a lightweight `GET /healthz` probe endpoint. The Compose example uses that same `/healthz` path for its container healthcheck.
Expand Down
Loading
Loading