@visulima/notification 1.2.0 → 2.0.1

package/CHANGELOG.md

@@ -1,3 +1,117 @@
+## @visulima/notification [2.0.1](https://github.com/visulima/visulima/compare/@visulima/notification@2.0.0...@visulima/notification@2.0.1) (2026-10-23)
+
+
+### Dependencies
+
+* **@visulima/email:** upgraded to 4.1.0
+
+## @visulima/notification [2.0.0](https://github.com/visulima/visulima/compare/@visulima/notification@1.2.0...@visulima/notification@2.0.0) (2026-10-15)
+
+### ⚠ BREAKING CHANGES
+
+* Deno is no longer a supported runtime or package manager.
+vis targets node/bun runtimes and aube/npm/pnpm/yarn package managers; the
+deno-lint/deno-fmt adapters and deno inference targets are removed.
+
+* fix: resolve eslint errors after deno removal
+
+- vis: use a block body for applyIgnoreScripts (arrow-body-style)
+- is-ansi-color-supported: drop stale eslint-disable directives and
+  replace the raw-release if/else with a ternary (unicorn/prefer-ternary)
+
+* docs(cron-parser): remove remaining deno runtime mentions
+
+These doc/config files arrived with main's dialect-gating commit after this
+branch's base, so they still listed Deno as a supported runtime.
+
+* feat!: remove deno runtime and tooling support
+
+Deno is being wound down: Cloudflare is acquiring the Deno team, the runtime
+gets one more year of monthly maintenance before development ends, and Deno
+Deploy shuts down. Drop Deno as a supported runtime, package manager, and
+lint/fmt/inference target across the monorepo.
+
+- vis: remove the deno runtime path, deno-lint/deno-fmt adapters, the
+  deno.json inference detector, Deno PM handling (TypeScript + Rust native
+  resolver), and the devcontainer deno mount; regenerate the JSON schemas.
+- libraries: drop Deno runtime detection from cerebro, ono,
+  is-ansi-color-supported, and task-runner command parsing; remove Deno
+  wording from package docs and READMEs.
+- delete the examples/deno directories (ono, pail, storage) and Deno docs.
+- keep JSR publishing (registry usable from Node), license/attribution
+  comments, the secret-scanner Deno-token rule, and the historical RFCs.
+* Deno is no longer a supported runtime or package manager.
+vis targets node/bun runtimes and aube/npm/pnpm/yarn package managers; the
+deno-lint/deno-fmt adapters and deno inference targets are removed.
+
+* fix: resolve eslint errors after deno removal
+
+- vis: use a block body for applyIgnoreScripts (arrow-body-style)
+- is-ansi-color-supported: drop stale eslint-disable directives and
+  replace the raw-release if/else with a ternary (unicorn/prefer-ternary)
+
+* chore(vis): tidy deno-removal leftovers from review
+
+* fix(vis): drop unused logger from x handler, restore bun typing
+
+Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
+
+* docs: add migration notes for removed deno exports
+
+Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
+
+* feat(vis): warn on stale adapter ids and deno-only projects
+
+Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
+
+* refactor(vis): derive runtime ids and reuse bun detection
+
+Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
+
+* refactor(vis): drop jsr deno option and deno auth reference
+
+Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
+
+* fix(vis): restore runtime id schema description
+
+Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
+
+* refactor(vis): remove jsr publishing support
+
+Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
+
+* feat(bytes): port @std/bytes helpers back in
+
+Carries the Uint8Array helpers from @std/bytes@1.0.6 (MIT, Copyright the Deno authors)
+into src/std-bytes.ts and re-exports them from the package entry. Keeps the public API that
+the Deno-removal commit dropped, without the jsr: devDependency. Docs and AGENTS notes are
+restored to describe the ported functions.
+
+Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
+
+* docs(bytes): attribute ported @std/bytes source
+
+The license file still listed @jsr/std__bytes as a bundled dependency.
+Replace it with the MIT notice for the ported src/std-bytes.ts, placed outside
+the generated dependency blocks.
+
+Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
+
+* fix(cron-parser): keep reviewed docs and 1.1.0 version
+
+The rebase onto the remote branch dropped the reviewed dialect sentence in the README and
+the installation table row, and the release commit's 1.1.0 version bump.
+
+### Features
+
+* remove deno runtime and tooling support ([#973](https://github.com/visulima/visulima/issues/973)) ([26fada1](https://github.com/visulima/visulima/commit/26fada1ac04731cba9db8f74fe20849c0a15db74))
+
+
+### Dependencies
+
+* **@visulima/email:** upgraded to 4.0.0
+* **@visulima/workflow:** upgraded to 4.0.0
+
 ## @visulima/notification [1.2.0](https://github.com/visulima/visulima/compare/@visulima/notification@1.1.23...@visulima/notification@1.2.0) (2026-10-08)
 
 ### Features

package/README.md

@@ -38,7 +38,7 @@
 typed facade drives many channel providers (SMS, push, chat, in-app, webhook) and the email channel delegates straight to
 `@visulima/email`. It is **infra-free** (no Redis/Mongo/dashboard required), **ESM-only**, **tree-shakeable** (import only
 the providers you use), and **edge-ready** — every native provider is built on `fetch` with zero Node built-ins, so it
-runs unmodified on Cloudflare Workers, Vercel Edge, Deno and Bun.
+runs unmodified on Cloudflare Workers, Vercel Edge and Bun.
 
 ## Install
 
@@ -57,7 +57,7 @@ pnpm add @visulima/notification
 ## Usage
 
 > **Every provider is `fetch`-based** — no per-provider SDK to install, and it runs on Node, Cloudflare Workers, Vercel
-> Edge, Deno and Bun. Optional peers are only needed by specific subpaths (e.g. `liquidjs` for `./template/liquid`,
+> Edge and Bun. Optional peers are only needed by specific subpaths (e.g. `liquidjs` for `./template/liquid`,
 > `@visulima/workflow` for `./workflow`) — see the [install table](https://visulima.com/docs/packages/notification/installation#optional-peer-dependencies).
 > Beyond sending, the package ships [workflows](https://visulima.com/docs/packages/notification/workflow),
 > [digest](https://visulima.com/docs/packages/notification/digest),
@@ -132,7 +132,7 @@ Providers are imported from `@visulima/notification/providers/<name>` so unused
 | **Wrappers** | `failover`, `roundrobin`, `opentelemetry`, `mock`               |
 
 > **Cloudflare / edge note:** nearly every provider is `fetch` + Web Crypto only and runs on **Cloudflare Workers**,
-> Vercel Edge, Deno and Bun — including **AWS SNS** (Web Crypto SigV4) and **web-push** (Web Crypto VAPID + RFC 8291).
+> Vercel Edge and Bun — including **AWS SNS** (Web Crypto SigV4) and **web-push** (Web Crypto VAPID + RFC 8291).
 > FCM accepts a `getAccessToken` callback so you bring your own OAuth token without a Node-only SDK. The only **Node-only**
 > pieces are **APNs** (`node:http2`) and the **bullmq / pg-boss / sqs** queue adapters — import those from a Node runtime.
 > See the [runtime matrix](https://visulima.com/docs/packages/notification/installation#runtime-support).
@@ -317,7 +317,7 @@ barrel holds the shared types, `createInboundRouter` and verification/reply help
 import { createSlackReceiver } from "@visulima/notification/providers/slack";
 
 // Read the secret however your runtime exposes it: an `env` binding on
-// Cloudflare Workers, `Deno.env.get`, `process.env` on Node.
+// Cloudflare Workers, `process.env` on Node.
 declare const signingSecret: string;
 
 const slack = createSlackReceiver({
@@ -331,7 +331,7 @@ const slack = createSlackReceiver({
     },
 });
 
-// Cloudflare Workers / Deno / Bun / Hono / Next.js route handlers …
+// Cloudflare Workers / Bun / Hono / Next.js route handlers …
 export default { fetch: (request: Request) => slack.handle(request) };
 ```
 

package/dist/inbound/index.d.ts

@@ -77,7 +77,7 @@ declare const chatReply: (provider: string, message: InboundMessage, outbound: P
 declare const smsReply: (message: InboundMessage, outbound: Provider<unknown, SmsPayload> | undefined) => InboundReplyFunction;
 /**
  * A web-standard request handler: the shape returned by {@link createInboundRouter} and the
- * signature platforms like Cloudflare Workers, Deno, Bun and Node's `fetch` server expect.
+ * signature platforms like Cloudflare Workers, Bun and Node's `fetch` server expect.
  * @param request The inbound request.
  * @returns The response.
  */
@@ -88,7 +88,7 @@ type FetchHandler = (request: Request) => Promise<Response>;
  * path-segment boundary, so a mount base path does not need to be known ahead of time. The most
  * specific route wins; unmatched paths get a `404`.
  *
- * The result is directly usable as a Cloudflare Workers / Deno / Bun `fetch` export, or via a
+ * The result is directly usable as a Cloudflare Workers / Bun `fetch` export, or via a
  * Node/Express/Hono web-request adapter.
  * @param routes A map of path (e.g. `"/webhooks/slack"`) to channel receiver.
  * @returns A fetch handler dispatching to the matching channel.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@visulima/notification",
-  "version": "1.2.0",
+  "version": "2.0.1",
   "description": "A reusable, ESM-only, edge-ready multi-channel notification library with SMS, push, chat, in-app and webhook providers",
   "keywords": [
     "agent",
@@ -238,11 +238,11 @@
   "peerDependencies": {
     "@aws-sdk/client-sqs": "^3.0.0",
     "@opentelemetry/api": "^1.0.0 || ^2.0.0",
-    "@visulima/email": "3.0.28",
-    "@visulima/workflow": "3.0.0",
+    "@visulima/email": "4.1.0",
+    "@visulima/workflow": "4.0.0",
     "bullmq": "^5.0.0",
     "croner": "^10.0.1",
-    "handlebars": ">=4.7.9",
+    "handlebars": ">=4.7.10",
     "intl-messageformat": "^11.0.0",
     "liquidjs": "^10.0.0",
     "pg-boss": "^10.0.0",