@zerotal/notifications 1.4.0 → 1.5.1

package/CHANGELOG.md

@@ -4,10 +4,44 @@ All notable changes to this package are documented here. The format is
 based on [Keep a Changelog](https://keepachangelog.com/); this package
 follows the Zerotal monorepo's unified versioning.
 
-**Maturity: `beta`**
+**Maturity: `stable`**
 
 ## [Unreleased]
 
+## [1.5.0] — 2026-08-15
+
+### Added
+
+- **Tests for `ResendDriver`.** Unlike SMTP, this driver's correctness is entirely
+  the shape of one JSON request, and every way of getting it wrong is quiet in
+  development — a stub answers 200 either way. Pinned: the bearer token and
+  endpoint, `Name <addr>` formatting, optional keys omitted rather than sent empty
+  (Resend rejects `cc: []`), `replyTo` mapped to the API's `reply_to` (sending the
+  camelCase key is accepted and silently ignored, so replies would go to the
+  sender), base64 encoding for both string and binary attachments, and
+  `content_type` / `content_id` key names. Plus the half that matters most: a
+  non-2xx raises, because a mail driver that swallows a 401 reports every send as
+  delivered while nothing arrives. 173 tests → 185.
+
+- **27 exports gained documentation** — the channel classes behind each channel
+  name, the three mail drivers, the delivery events (`NotificationSent`,
+  `MessageSent`, `MessageFailed`, `MessageQueued`), the full error table,
+  `OnDemandNotifiable`, `RichLine`, and the `recentDeliveries()` / `channelStats()`
+  counters the admin console renders. The broadcast wire event is now named as
+  `BROADCAST_NOTIFICATION_EVENT` where its value was already documented.
+
+### Changed
+
+- **Five exports are marked `@internal`** — `SendNotificationJob`,
+  `BroadcastNotificationJob`, `validateNotificationConfig` and the two command
+  classes. Queue-serialisation plumbing and CLI wiring, none of it API: you queue
+  through `notifyLater()` and run the commands through `bun zt`. The promise is 38
+  exports, not 43.
+
+- **Maturity is now `stable`** — the public API follows SemVer strictly for the rest
+  of the 1.x line. Every promised export is documented and the transports are
+  covered, including the HTTP driver whose failures are otherwise invisible.
+
 ## [1.0.3] — 2026-08-07
 
 ### Changed

package/package.json

@@ -1,8 +1,8 @@
 {
   "name": "@zerotal/notifications",
-  "version": "1.4.0",
+  "version": "1.5.1",
   "license": "MIT",
-  "maturity": "beta",
+  "maturity": "stable",
   "private": false,
   "type": "module",
   "main": "./src/index.ts",
@@ -29,12 +29,12 @@
     "typecheck": "tsc --noEmit"
   },
   "dependencies": {
-    "@zerotal/core": "1.4.0",
-    "@zerotal/orm": "1.4.0",
-    "@zerotal/queue": "1.4.0"
+    "@zerotal/core": "1.5.1",
+    "@zerotal/orm": "1.5.1",
+    "@zerotal/queue": "1.5.1"
   },
   "devDependencies": {
-    "@zerotal/broadcasting": "1.4.0",
+    "@zerotal/broadcasting": "1.5.1",
     "typescript": "^5.8.0"
   },
   "description": "Multi-channel notifications for Zerotal — mail (SMTP/Resend), database, broadcast, Slack, and SMS.",

package/src/BroadcastNotificationJob.ts

@@ -8,6 +8,8 @@ import { Job, JobRegistry } from "@zerotal/queue";
  * the whole point of the channel is immediacy. Its payload is the resolved wire
  * data, so it round-trips through a persistent driver without needing the
  * notification class.
+ *
+ * @internal
  */
 export class BroadcastNotificationJob extends Job {
   override readonly queue: string;

package/src/Notifiable.ts

@@ -91,5 +91,5 @@ export function Notifiable<TBase extends Constructor>(Base: TBase) {
  * value (the mixin) and a type (the contract) — it merges with the function above. Extends the
  * base notifiable contract, so instances pass anywhere a notifiable is expected.
  */
-// eslint-disable-next-line @typescript-eslint/no-empty-object-type -- the empty body is the point: it merges the name with the mixin function above
+// The empty body is the point: it merges the name with the mixin function above.
 export interface Notifiable extends NotifiableContract {}

package/src/SendNotificationJob.ts

@@ -18,6 +18,8 @@ import {
  * (SQLite/Redis) it holds only the serialized snapshot written by `payload()`, and
  * rebuilds both sides in `handle()` — asynchronously, because resolving a
  * notification class may require importing `app/notifications/`.
+ *
+ * @internal
  */
 export class SendNotificationJob extends Job {
   override readonly queue = "notifications";

package/src/commands/NotificationsPruneCommand.ts

@@ -8,6 +8,8 @@ import type { NotificationManager } from "../NotificationManager.ts";
  * The database channel never removes anything on its own, so an app that has
  * been notifying users for a year is carrying a year of rows. Run this on a
  * schedule.
+ *
+ * @internal
  */
 export class NotificationsPruneCommand extends Command {
   static commandName = "notifications:prune";

package/src/commands/NotificationsTestCommand.ts

@@ -28,6 +28,8 @@ class TestNotification extends Notification {
  * Mail configuration fails in ways unit tests cannot reach: a wrong port, a
  * refused STARTTLS upgrade, credentials the server rejects. This exercises the
  * whole path and prints what the server said.
+ *
+ * @internal
  */
 export class NotificationsTestCommand extends Command {
   static commandName = "notifications:test";

package/src/config.ts

@@ -59,6 +59,8 @@ export function NotificationConfig(
  * naming the key — rather than on the first password-reset email of the day.
  *
  * @throws {NotificationConfigError} on the first inconsistency found.
+ *
+ * @internal
  */
 export function validateNotificationConfig(config: NotificationConfigShape): void {
   const { mail, sms } = config;