Release v0.14.0

Author: hugobessa

CHANGELOG.md

@@ -1,5 +1,16 @@
 # Changelog
 
+# Version 0.14.0
+
+* Added multi-tenant support via a new optional `tenant` field on notifications. Notifications can now be scoped to a specific tenant (e.g. an organization, clinic, or workspace), and `filterNotifications` accepts a `tenant` filter that returns only notifications belonging to the given tenant(s).
+  * **Core types**: `NotificationInput`, `NotificationResendWithContextInput`, `OneOffNotificationInput`, and `OneOffNotificationResendWithContextInput` accept an optional `tenant?: string | null`. `DatabaseNotification` and `DatabaseOneOffNotification` include a `tenant: string | null` field. `NotificationFilterFields` accepts `tenant?: string | string[]`, and `'fields.tenant'` was added to the default backend filter capabilities.
+  * **Tenant reassignment is forbidden on update.** The service methods `updateNotification` and `updateOneOffNotification` now statically `Omit<'tenant'>` from their partial payloads and throw at runtime if a `tenant` key is present. Backends also enforce this defensively: both `vintasend-prisma` and `vintasend-medplum` read the existing resource and reject any update whose incoming tenant differs from the current tenant. Idempotent updates (same tenant, or no `tenant` field) are still allowed so multi-backend replication continues to work.
+* **`vintasend-prisma`**: `PrismaNotificationModel` now has a `tenant: string | null` column. The Prisma `where` conversion supports `tenant` filters (single value, array, and negation). Consumers must run a migration adding a nullable `tenant` text column (and ideally an index) to their notification table.
+* **`vintasend-medplum`**: Tenant support uses Medplum's native compartment mechanism. On persist, `meta.accounts` is set directly on the `Communication` resource inline (no separate `$set-accounts` call), so Medplum populates `meta.compartment` server-side and your `AccessPolicy` with parameterized compartment variables scopes reads automatically. On query, `tenant` filters are translated to the FHIR `_compartment` search parameter. See: https://www.medplum.com/docs/access/multi-tenant-access-policy
+* **`vintasend-dashboard`**: Added a tenant text filter to the notifications filter bar, a tenant column to the notifications table, a tenant field to the notification detail view, and URL query param sync for the `tenant` filter (bookmarkable/shareable URLs).
+* Updated the notification resend reconstruction in the service layer so `tenant` is carried through, and added `'tenant'` to the multi-backend sync verification field list.
+* Updated the example Prisma schema in `examples/nextjs-prisma-nodemailer-pug-temporal` to document the required column and index.
+
 # Version 0.13.3
 
 * Refactor compile-pug-templates script to be compatible with Node 20.x

package.json

@@ -1,6 +1,6 @@
 {
   "name": "vintasend",
-  "version": "0.13.3",
+  "version": "0.14.0",
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",
   "exports": {

src/implementations/vintasend-implementation-template/package.json

@@ -1,6 +1,6 @@
 {
   "name": "vintasend-implementation-template",
-  "version": "0.10.0",
+  "version": "0.14.0",
   "description": "",
   "type": "module",
   "main": "dist/index.js",
@@ -18,7 +18,7 @@
   "author": "Hugo Bessa",
   "license": "MIT",
   "dependencies": {
-    "vintasend": "^0.13.0"
+    "vintasend": "^0.14.0"
   },
   "devDependencies": {
     "@biomejs/biome": "^2.4.5",

src/implementations/vintasend-implementation-template/src/__tests__/adapter.test.ts

@@ -63,6 +63,7 @@ describe('NotificationAdapter', () => {
       bodyTemplate: '/path/to/template',
       subjectTemplate: '/path/to/subject',
       extraParams: {},
+      tenant: null,
       contextUsed: null,
       adapterUsed: null,
       status: 'PENDING_SEND' as const,
@@ -149,6 +150,7 @@ describe('NotificationAdapter', () => {
         bodyTemplate: '/path/to/template',
         subjectTemplate: '/path/to/subject',
         extraParams: {},
+        tenant: null,
         contextUsed: null,
         adapterUsed: null,
         status: 'PENDING_SEND' as const,

src/implementations/vintasend-implementation-template/src/__tests__/template-renderer.test.ts

@@ -29,6 +29,7 @@ describe('TemplateRenderer', () => {
       bodyTemplate: '/path/to/template',
       subjectTemplate: '/path/to/subject',
       extraParams: {},
+      tenant: null,
       contextUsed: null,
       adapterUsed: null,
       status: 'PENDING_SEND' as const,

src/services/__tests__/multi-backend-error-handling.test.ts

@@ -112,6 +112,7 @@ describe('VintaSend multi-backend error handling (Phase 4)', () => {
     sendAfter: new Date(Date.now() + 60_000),
     subjectTemplate: 'subject',
     extraParams: null,
+    tenant: null,
   };
 
   const databaseNotification = {

src/services/__tests__/multi-backend-management.test.ts

@@ -118,6 +118,7 @@ function createDatabaseNotification(
     status,
     contextUsed: null,
     extraParams: null,
+    tenant: null,
     adapterUsed: null,
     sentAt: null,
     readAt: null,

src/services/__tests__/multi-backend-writes.test.ts

@@ -121,6 +121,7 @@ describe('VintaSend multi-backend writes (Phase 4)', () => {
     sendAfter: new Date(Date.now() + 60_000),
     subjectTemplate: 'subject',
     extraParams: null,
+    tenant: null,
   };
 
   const baseOneOffInput: Omit<OneOffNotificationInput<Config>, 'id'> = {
@@ -135,6 +136,7 @@ describe('VintaSend multi-backend writes (Phase 4)', () => {
     sendAfter: new Date(Date.now() + 60_000),
     subjectTemplate: 'subject',
     extraParams: null,
+    tenant: null,
   };
 
   beforeEach(() => {

src/services/__tests__/notification-service-one-off.test.ts

@@ -125,6 +125,7 @@ describe('NotificationService - One-Off Notifications', () => {
       status: 'PENDING_SEND' as const,
       contextUsed: null,
       extraParams: {},
+      tenant: null,
       adapterUsed: null,
       sentAt: null,
       readAt: null,

src/services/__tests__/notification-service.test.ts

@@ -112,6 +112,7 @@ describe('NotificationService', () => {
     bodyTemplate: '/path/to/template',
     subjectTemplate: '/path/to/subject',
     extraParams: {},
+    tenant: null,
     contextUsed: null,
     adapterUsed: null,
     status: 'PENDING_SEND' as const,
@@ -140,6 +141,7 @@ describe('NotificationService', () => {
       bodyTemplate: '/path/to/template',
       subjectTemplate: '/path/to/subject',
       extraParams: {},
+      tenant: null,
       contextUsed: null,
       adapterUsed: null,
       status: 'PENDING_SEND' as const,
@@ -394,6 +396,7 @@ describe('NotificationService', () => {
       bodyTemplate: '/path/to/template',
       subjectTemplate: '/path/to/subject',
       extraParams: {},
+      tenant: null,
       contextUsed: null,
       adapterUsed: null,
       status: 'PENDING_SEND' as const,
@@ -517,6 +520,7 @@ describe('NotificationService', () => {
       bodyTemplate: '/path/to/template',
       subjectTemplate: '/path/to/subject',
       extraParams: {},
+      tenant: null,
       contextUsed: null,
       adapterUsed: null,
       status: 'PENDING_SEND' as const,