Repository navigation
v0.1.9
Doca 0.1.9
Changes
- Store immutable plugin ZIPs in host-managed file storage. The shared database holds the desired installation list, archive references and file hashes. Each instance verifies its local code cache and restores missing or damaged files at startup, without contacting the plugin store or running package installation/build scripts.
- Add public SDK services for plugin-owned structured SQL databases and private binary objects. Bind handles to the plugin ID, data version and installation generation; namespace tables, ordinary files and object paths to avoid host/plugin collisions. Disabling preserves data; uninstalling fences old handles and clears private data while retaining user files and historical releases.
- Move file-store configuration and credentials to
DOCA_FILE_STORE_IDandDOCA_FILE_STORES_JSON. The administration page displays the selected backend read-only. Container defaults use local storage at/data/storage; replicas must use the same persistent backend. - Add public rich-text/spreadsheet plugin elements, host assistant launch APIs, template/material retrieval and reusable pickers. Include prebuilt SDK examples for elements and storage; these are not installed in the production image by default.
- Fix Markdown's first-edit checkpoint handling, same-version reinstall restart status, immediate knowledge-source subscription refresh, and the retired template administration navigation entry.
- Report the host package version consistently in health, readiness, liveness and OpenAPI responses.
Breaking deployment requirements
This release intentionally does not support old versions. The host baseline is doca-2026-10-03-storage-v1, the shared plugin registry is version 2, and plugin packages must declare doca.storage: "host" with an SDK range whose minimum is at least 0.1.7. Old databases, installation lists, storage configuration and SDK ranges are rejected, without migration, conversion or deletion of old data.
Deploy to a new empty database and a separate persistent storage location. Preserve the old deployment, database and storage for rollback; new deployment data remains separate. Rebuild business plugins against SDK 0.1.7 and supply the required storage declaration. Shared PostgreSQL, Redis and file storage are required for multiple instances. Restart every instance manually after plugin changes; a response only reports the serving instance's running selection, not cluster-wide completion.
SDK scope enforces public service isolation, but trusted Node.js plugins are not operating-system sandboxes. Private object uploads whose database commit fails can leave unreferenced bytes; automatic orphan scanning is not provided.
Public npm packages
@smartdoca/plugin-sdk@0.1.7@smartdoca/plugin-contracts@0.1.6@smartdoca/web-plugin-registry@0.1.3
File, search and knowledge capability packages remain at 0.1.1. Package publication is verified separately from source version changes.
Validation
The default suite passed 1,166 tests across 179 files, with three environment-conditional tests skipped. PostgreSQL/Redis checks separately passed all three conditional cases. TypeScript, the web build and independent SDK JavaScript/declaration consumers passed. Local browser acceptance used two independent instances with shared PostgreSQL, Redis and file storage; see the detailed report.
Both Linux amd64 and arm64 container images passed fresh-database bootstrap, healthy startup, login, SDK database writes/reads, private object roundtrip, ordinary file creation, content source discovery, static assets and restart with persisted state. Health/OpenAPI versions were checked against 0.1.9.
Real AI/mail/SSO/Webhook/S3/CDN services, mobile device builds, slideshow fullscreen and every editor menu are not claimed as completed acceptance. No production user data was used.
Distribution
GitHub tag: v0.1.9. Docker images: docker.io/smartdoca/doca:0.1.9 and docker.io/smartdoca/doca:latest, for Linux amd64 and arm64. The GitHub Release includes web assets and SHA-256 checksums; publish the unpacked assets directory unchanged when using DOCA_ASSET_BASE.
Web assets are attached as doca-web-assets-v0.1.9.tar.gz. Verify SHA256SUMS, extract the archive and publish its assets directory unchanged. Set DOCA_ASSET_BASE to the HTTPS prefix containing that directory, with cross-origin module access enabled. Do not use the GitHub download URL as the asset base.
Release source: PR #32. Docker manifest and npm package checksums are recorded in release-manifest.json.