Breaking Changes
sign → certify rename
All signing API surfaces have been renamed:
Old names still work — they are exported as deprecated aliases. No immediate code changes are required, but you should migrate before a future major version removes the aliases.
Migration Examples
React (<Document> prop)
Node.js (@formepdf/core)
API endpoint
Go SDK
Python SDK
New in 0.9.0
New API Endpoints
New Features
- Documents archive — every render auto-saved with metadata
- Certificate storage — save certificates, reference by ID
- Redaction templates — reusable pattern sets
- Text-search redaction — literal, regex, and preset patterns
- Audit trail — full operation history on documents
- Developer metadata — tag renders with custom key-value pairs
- Resource listing — list templates, documents, certificates via API
Bug Fixes
- SVG children API — JSX children auto-serialized to SVG content
- SVG opacity support (opacity, fill-opacity, stroke-opacity)
- Page style prop inheritance fix
- WASM time panic fix in certify and redact (browser WASM)
- PKCS#1 private key auto-conversion to PKCS#8
Upgrade Checklist
- Update
@formepdf/react,@formepdf/core, and@formepdf/clito 0.9.0 - Search your codebase for
signatureprop,signPdf,SignatureConfig,/v1/sign - Replace with
certification,certifyPdf,CertificationConfig,/v1/certify - Update Go/Python SDK method calls if applicable
- Test that existing certifications still verify correctly