Skip to content

v0.1.10

Choose a tag to compare

View all tags
@github-actions github-actions released this 03 Oct 23:30
· 48 commits to main since this release
v0.1.10
23def4b
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Doca 0.1.10

Changes

  • Add host-managed plugin credentials through storage.credentials.v1: server-only encrypted create/read/inspect, revision-checked update/delete, plugin identity and installation generation isolation, and cleanup on uninstall. The environment supplies a shared DOCA_CREDENTIAL_MASTER_KEY; missing, invalid or mismatched keys fail explicitly without generating or replacing a key.
  • Add material collections in SDK 0.1.9 / contracts 0.1.7. Materials may belong to zero or multiple collections. Search and AI retrieval return separate material/collection groups with independent tags and pagination. Collection metadata is lightweight; members are queried separately and permissions/revisions are checked before use.
  • Unify template and material browsing: two compact rows for sources and tags, defaulting to All, with source multi-selection. The filter icon opens keyword/smart search and sorting. Submitted search terms remain visible and can be cleared. Cards show previews and source information; blank document creation remains available.
  • Forward database, Redis, cloud file storage and credential-key settings through Compose. Storage backends remain deployment-owned; the administration interface displays storage state without accepting backend credentials.
  • Drain both material/collection query groups before returning a rejection, so a provider being disposed cannot leave its sibling using a database connection after the request ends.
  • Keep host version reporting in the application module and exclude local plugin ZIP archives from Git.
  • Rebuild the storage acceptance example as 1.0.5 against SDK 0.1.9, with a materials.v2 provider and explicit collection capability.

Breaking deployment requirements

The database baseline is doca-2026-10-03-credentials-v2. Databases from 0.1.9 and earlier are rejected without migration, conversion, automatic table creation or data deletion. Preserve the old deployment, database and storage for rollback; use a new empty database and separate persistent storage for this release. New deployment data remains separate when rolling back.

Material providers now implement materials.v2, declare version: 2, and explicitly declare their collections capability (methods or null). materials.v1 is rejected without an adapter. Existing files, documents and resource references are preserved. Template providers remain on templates.v1.

Plugins must declare doca.storage: "host" and an SDK range covering 0.1.9 whose minimum meets the existing 0.1.7 installation floor. Rebuild material providers against SDK 0.1.9. Plugins using managed credentials must require the public credential token and deployments must retain the same master key across restarts and replicas. Restart every instance manually after plugin changes.

Packages and distribution

  • @smartdoca/plugin-sdk@0.1.9
  • @smartdoca/plugin-contracts@0.1.7
  • File/search/knowledge capability packages remain 0.1.1; web plugin registry remains 0.1.3.
  • GitHub tag v0.1.10; Docker images docker.io/smartdoca/doca:0.1.10 and latest, for Linux amd64 and arm64.
  • GitHub Release attaches Web assets, SDK/contract tarballs, SHA-256 checksums and a release manifest. The manifest records final registry digests and verification results.

Validation and limits

The default suite passed 1,193 tests across 182 files, with three environment-conditional tests skipped. All 71 targeted PostgreSQL/Redis checks passed, including the three conditional cases. TypeScript, Web production build, the independent SDK JavaScript/declaration consumer and the packed npm consumer passed. Source browser acceptance covered material/template filters, smart search, previews, and narrow-screen filter positioning in isolated fixtures. Credential browser acceptance used isolated databases and synthetic secrets; see the report.

Release artifact verification includes packed/public npm consumers and fresh-database container startup for both supported Linux architectures. Final results are recorded in the release manifest. Real external AI/mail/SSO/Webhook/S3/CDN services and native mobile builds are not claimed as verified. No production user data is used for release checks.

Downloads

Extract doca-web-assets-v0.1.10.tar.gz and publish its assets directory unchanged. Set DOCA_ASSET_BASE to the HTTPS prefix containing that directory, without a trailing slash. release-manifest.json records package integrity, image digest, source revisions and artifact verification; SHA256SUMS covers the attached files.

Assets 7
Loading