@voltro/plugin-moderation 0.87.0 → 0.88.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (6) hide show
  1. package/CHANGELOG.md +169 -6
  2. package/THIRD-PARTY-NOTICES.md +649 -53
  3. package/dist/errors.js +1 -2
  4. package/dist/index.js +1 -2
  5. package/dist/providers.js +1 -2
  6. package/package.json +5 -5
package/CHANGELOG.md CHANGED
@@ -41,6 +41,166 @@ _Changes staged for the next release accumulate here (rolled up from
41
41
 
42
42
  ---
43
43
 
44
+ ## [0.88.0] — 2026-11-02
45
+
46
+ ### ⚠ BREAKING
47
+
48
+ - **Direct computed-cache key callers handle unencodable subjects** — `@voltro/runtime`, `@voltro/voltro`
49
+
50
+ `computedCacheKey()` can return `bypass: 'subject-not-encodable'` for claims that cannot safely identify a cache entry. Direct consumers with exhaustive bypass switches must handle this case by running without caching. `voltro update` identifies the direct imports to review. Queries using the native `cache:` declaration and `invoke()` tests need no manual key or code change.
51
+ - **The framework runs on effect 4.1.0** — `@voltro/cli`, `@voltro/devtools`, `@voltro/runtime`, `@voltro/database`, `@voltro/voltro`, `@voltro/sql-sqlite`, `@voltro/sql-mysql`, `@voltro/sql-mssql`, `@voltro/sql-postgres`
52
+
53
+ Every `@voltro/*` package now pins `effect` and its `@effect/*` companions to 4.1.0. Apps pin the same version and run `voltro add patches`: it writes the 4.1.0 patch files, retires the `patchedDependencies` entries an earlier CLI shipped for 4.0.1 (pnpm refuses an install over an unused patch) and moves the lockstep overrides. Two former patch fixes ship upstream in 4.1.0 (SQL Server request cancellation, the SQL Server message-storage MERGE). On SQL Server the shared transaction key now applies to every client in the process, not only the first one built.
54
+
55
+ `chunkRowsForInsert` from `@voltro/database` returns non-empty chunks (`NonEmptyReadonlyArray`), the shape effect 4.1's `sql.insert` requires; an empty input yields no chunk instead of one empty chunk.
56
+
57
+ SQL statement spans are named after their database, following the OpenTelemetry database conventions: the database name, else the server address, else the system name (`postgresql`, `mysql`, `microsoft.sql_server`, `sqlite`). Before, every statement span was `sql.execute`. Trace queries and dashboards that match that name should match the `db.query.text` attribute instead; the devtools trace panel and durable-trace sampling already do.
58
+
59
+ **`voltro update` carries you across this** — codemod `0.88.0/01_effect-4-1`. If you pin versions by hand and never run it, print the notes without changing anything: `voltro update --codemods-only --from <your current version> --dry-run` (this one ships in 0.88.0).
60
+ - **Runtime patch pins preserve third-party Effect majors** — `@voltro/cli`
61
+
62
+ `voltro add patches` scopes Effect pins to their current major instead of replacing unrelated libraries' Effect 3 dependencies. It migrates exact pins previously shipped by the framework, preserves unrelated policies, and refuses conflicting custom policies before writing files. In pnpm workspaces it names competing nonempty root `resolutions` or `pnpm.overrides` and explains their explicit reconciliation. Peer repair refuses cross-major global policy changes. Bun workspaces require Bun >=1.4.4 and a supported `packageManager` pin or `engines.bun` floor; upgrade the actual tool and older declarations before retrying, because Bun 1.2.0 ignored the scoped companion pin. `voltro update` carries the review as `0.88.0/06_effect-override-scope`.
63
+ - **Keep test runners out of production KV and workflow dependency closures** — `@voltro/kv`, `@voltro/workflow`
64
+
65
+ The test-only HotStore and workflow conformance suites now require their caller to supply runner operations. Pass `{ describe, it, expect }` as the third argument to `hotStoreConformance`, and `{ describe, test, expect, beforeAll, afterEach }` as the second argument to `runClusterEngineSuite` and `runJournalEncryptionSuite`. The exported structural runner interfaces have no dependency on Vitest. Both production packages remove their optional Vitest peer; an application's development runner can no longer enter a production deployment through those peer links. Keep Vitest in the test application's own devDependencies. Runtime KV/workflow calls and `runHotStoreSqlParity` are unchanged. `voltro update` identifies direct suite imports for review.
66
+ - **REST test handlers publish events under the request tenant** — `@voltro/testing`, `@voltro/cli`
67
+
68
+ When crossing 0.87.0, custom `makeTestApp({ restRoutes })` handlers receive a request-scoped `ctx.app` instead of the root fixture context. Event assertions must subscribe to that request tenant: the default anonymous request uses `acme` or `x-tenant`; an explicit `anonymous: 'no-tenant'` uses `''`, distinct from the event bus subscriber's default `null`. Pass the app's anonymous policy, select the subscriber tenant explicitly and assert delivered payloads even when HTTP success and `notified` already pass. Direct `invoke` retains its supplied context identity, and projected `publicApi` handlers already use request-scoped invocation. Plugin HTTP routes are not mounted by this request harness. `voltro update` locates raw request harness calls and prints the review steps.
69
+
70
+ ### Added
71
+
72
+ - **voltro add patches --ai accepts ai 7.0.156** — `@voltro/cli`, `@voltro/ai`
73
+
74
+ `voltro add patches --ai 7.0.156` wires the AI SDK declaration correction for `@ai-sdk/provider-utils` 5.0.70, regenerated with the original build from the release commit; JavaScript stays byte-identical to the published package. 7.0.105 and 7.0.132 remain selectable. `@voltro/ai` is built and tested against ai 7.0.156.
75
+ - **The retained invoice observations table is exported from the billing package** — `@voltro/plugin-billing`
76
+
77
+ `billingRetainedInvoiceObservationsTable` is exported from `@voltro/plugin-billing` beside the other billing tables, so an app can reference it.
78
+ - **plugin-billing accepts stripe 23** — `@voltro/plugin-billing`
79
+
80
+ The `stripe` peer range is `^22.6.1 || ^23.0.1`. stripe 23 pins Stripe API version `2026-09-30.endive`; the plugin still sends no `apiVersion` of its own, so the SDK's pinned version applies.
81
+
82
+ ### Changed
83
+
84
+ - **A booting server holds requests until the app is ready instead of answering 503** — `@voltro/runtime`, `@voltro/voltro`
85
+
86
+ `voltro serve`, `voltro start` and `voltro dev` used to answer every request that arrived before the boot finished with a plain-text `503 starting`. On a platform that scales to zero, that request is the visitor who woke the instance, and a browser does not act on `Retry-After` for a navigation. Requests and WebSocket upgrades that arrive while the app boots now wait and are handed to the app in arrival order once it is ready. The wait is bounded by `VOLTRO_BOOT_HOLD_MS` (default `30000`, at most five minutes, `0` restores the immediate `503`) and by 512 waiting requests. A request the wait cannot cover still gets `503` with `Retry-After: 1`, and a browser navigation gets a minimal page that reloads itself. `/internal/startup` reports waiting requests as `held`, and `bindBootListener` accepts `holdMs` and `maxHeld`. Probes are unchanged, so nothing changes under Kubernetes.
87
+ - **DocsLayout navigation nests collapsible groups with page counts** — `@voltro/ui-shadcn`
88
+
89
+ `DocsLayout` renders its sidebar as one tree: headerless groups are flat start links, other groups and sub-groups are collapsible rows with page counts, `DocsNavSubGroup` accepts nested `subgroups` and `trailingEntries`, the current page's link carries `aria-current="page"` (forwarded through `ShellLinkProps`), and the rail scrolls the active link into view after navigation.
90
+ - **Native Redis connections use ioredis 6 and keep the RESP2 protocol** — `@voltro/kv`, `@voltro/runtime`, `@voltro/cli`
91
+
92
+ The native Redis transport moved to ioredis 6, which defaults to RESP3. Registry connections set `protocol: 2`, so command replies, Pub/Sub and Lua results keep their shapes.
93
+ - **Connection drivers install only with the server runtime** — `@voltro/kv`, `@voltro/runtime`
94
+
95
+ `ioredis`, `@upstash/redis` and `@nats-io/transport-node` are optional peers of `@voltro/kv` and dependencies of `@voltro/runtime`. API apps keep all three without a step; web apps and SDKs that reach `@voltro/kv` only through types no longer download server drivers. Code that opens a connection without `@voltro/runtime` adds its driver, and a missing driver now fails naming the package.
96
+ - **The mobile template targets Expo SDK 58** — `@voltro/cli`
97
+
98
+ New mobile apps scaffold on Expo SDK 58 with React Native 0.88.1 and React 19.3.0, using the versions SDK 58 bundles for its native modules.
99
+ - **plugin-sentry runs on Sentry 11 and exports server spans over OTLP** — `@voltro/plugin-sentry`
100
+
101
+ Sentry 11 removed `SentrySpanProcessor`. The plugin now exports the framework's spans to the OTLP endpoint Sentry derives from the DSN and links errors and logs to the active span with `openTelemetryIntegration()`; the Sentry SDK records no spans of its own. `tracesSampleRate` keeps its meaning and is applied per trace id at the export. Server traces need the optional `@opentelemetry/sdk-trace-base` and `@opentelemetry/exporter-trace-otlp-http` packages (they replace `@sentry/opentelemetry`); without them the plugin warns and reports errors and breadcrumbs only. `init.tracesSampleRate` and `init.enableOpenTelemetrySetup` are ignored, and `init.skipOpenTelemetrySetup` no longer exists in Sentry 11.
102
+
103
+ ### Fixed
104
+
105
+ - **Deferred workflow starts retain their original caller receipt** — `@voltro/workflow`, `@voltro/cli`
106
+
107
+ A controlled workflow start now returns its existing queued receipt when another replica exhausts submission retries, or shared capacity moves, before its acceptance callback dispatches. It no longer reports an ordinary start failure while the committed submission remains unresolved. Execution identity, caller input, capacity ownership and retry limits stay unchanged; definite rejection and invalid ownership still fail explicitly.
108
+
109
+ - **Aggregate counters are non-negative safe integers on every dialect** — `@voltro/database`
110
+
111
+ A `count()` / `countDistinct()` / ranking counter now decodes to a number only when it is a non-negative safe integer; a fractional, negative, non-numeric or larger value is refused instead of passed through or rounded. SQLite and Turso decode counters too when the queried table has decimal columns, where they used to stay strings.
112
+ - **Cache clear honors connection namespace prefixes** — `@voltro/kv`, `@voltro/cache`
113
+
114
+ Clearing a cache through a named, namespaced Redis connection now binds logical cache keys to that connection's physical namespace. Redis-family engines and the local transport preserve neighboring caches and invalidation fences, while refusing foreign prefixes and forged key sets. The existing atomic cache command format remains unchanged.
115
+ - **Cache commands use the selected app's configuration and connections** — `@voltro/cli`
116
+
117
+ `voltro cache status`, `flush` and `invalidate` resolve `app.config.ts`, environment overrides and named Redis connections exactly like Dev and Serve, including an optional target app directory. Invalid configuration fails instead of silently reporting memory, in-process transports refuse CLI mutation, and diagnostics omit endpoint URLs and credentials.
118
+ - **Generated cache examples boot and upgrade reviews name affected lines** — `@voltro/cli`
119
+
120
+ The seeded core API example now uses an object cache declaration. Forced guide refresh discovers both flat and project-grouped app layouts, replacing stale nested examples without executing configs or crossing an app boundary. The shared cache/KV migration review lists authored code locations, including asserted backend literals, and a new review reaches applications that already crossed the original migration. It also identifies stale core guides for refresh; protected hand-maintained guides stay under their owner's control.
121
+ - **Subject query caches follow current authority** — `@voltro/runtime`, `@voltro/testing`
122
+
123
+ Subject-scoped computed queries key the complete subject claims and raw and resolved permission sets. Removing an admin grant, changing roles or switching tenant or credential type cannot reuse a result admitted under earlier authority. Authentication refreshes before lookup, and a change while a read is pending refuses retention and delivery. Connection-local state is never covered by subject scope; handlers that read it do not retain their results. The same decisions apply to `invoke` tests, memory caches and Redis caches.
124
+ - **Preserve connection declaration errors across module boundaries** — `@voltro/kv`
125
+
126
+ Redis, NATS, Storage, Analytics and SQL registries retain typed configuration diagnostics across module and VM boundaries instead of mislabeling them as dynamic credential failures. Errors returned by credential resolvers remain redacted.
127
+ - **Bind demo API tenants consistently in browser and server renders** — `@voltro/cli`
128
+
129
+ The fullstack, admin, SSR API and public status templates now send their explicit demo tenant to header-based anonymous APIs. SSR API and status pages use the same binding for server-side RPC reads, so a fresh scaffold renders successfully and its browser subscriptions select the same data. API refusals for missing tenants and access checks remain enforced. These demo bindings select rows and do not authenticate users; private production data requires verified authentication. Fresh-consumer diagnostics retain uppercase error log lines.
130
+ - **Two voltro dev processes starting together mint one set of secrets, not two** — `@voltro/cli`
131
+
132
+ `voltro dev` mints missing project secrets into `.env.local`. Two processes on one project starting at the same time (two local replicas, a dev server beside a test boot) each minted their own values; with field encryption the database recorded one key and refused the second process at boot. Minting now runs under a lock and adopts a value another process wrote meanwhile; a lock left by a crashed mint is taken over.
133
+ - **Event warnings follow workspace package exports** — `@voltro/cli`
134
+
135
+ Development event wiring warnings now recognise sibling `useEvent` consumers imported through package exports, TypeScript path aliases, named and namespace re-exports, and static local aliases. Each subscription is matched to its descriptor so an unused import or another API's same-named module does not hide a missing consumer. Workspace discovery supports declared pnpm, npm, Yarn and Bun members and excludes nested projects and build output.
136
+ - **Index audit preserves partial row coverage and uniqueness** — `@voltro/database`
137
+
138
+ The index audit recommends dropping an index only when another B-tree index preserves its row coverage and uniqueness. Partial unique indexes no longer make full indexes appear redundant; specialized index methods and unproved predicate relationships are excluded, and recommendations name only the safe replacement direction.
139
+ - **Migration logs identify which operations their count includes** — `@voltro/database`
140
+
141
+ Development auto-migration logs now identify their applied-operation count as the planner pass, excluding framework bootstrap and file-based migrations. A schema plan taken before boot can include work completed by those earlier stages; run a new plan after boot to verify that no operations remain.
142
+ - **Filter completed workflow pool owners before recovery transport** — `@voltro/cli`, `@voltro/voltro`, `@voltro/workflow`
143
+
144
+ Pool release recovery now persists its terminal settlement on submission and restart owners and filters those markers through indexed SQL predicates. Finished owner history no longer crosses the wire on every idle pass or after process restart. Lost release acknowledgements, held owners and missing evidence remain recoverable and reported; immutable owners and permit tombstones remain for receipt and replay safety. Normal framework schema migration adds two nullable settlement markers and their indexes; existing history is checked once in bounded pages. Settlement indexes use explicit short names within SQL identifier limits. Reconciliation cadence is unchanged.
145
+ - **Presence transport warnings follow actual subscription readiness** — `@voltro/plugin-presence`
146
+
147
+ Presence reports pending binding or subscription acquisition without a false missing-provider warning after five seconds. It reports cross-instance readiness only after acquiring the broadcast subscription, while local-only bindings and failed subscriptions still warn. Closing or replacing a binding prevents stale callbacks and releases subscriptions acquired afterward.
148
+ - **Self-updates finish after the old CLI installation is removed** — `@voltro/cli`, `@voltro/runtime`
149
+
150
+ `voltro update` loads its completion helpers before installing the target version, so removing the running CLI package no longer turns a successful upgrade into a missing-module failure. Error reporting uses the shared lightweight `@voltro/runtime/boot-refusal` entry loaded before dispatch; genuine failures keep their original message and exit code without loading the server dependency graph for help or version commands.
151
+ - **Compiled API servers start without a source-analysis dependency** — `@voltro/cli`
152
+
153
+ The development event-consumer audit loads its source compiler only when scanning. A compiled API server can start after relocation without app sources or a direct `ts-morph` dependency. Package-export consumer discovery keeps its existing scope and does not execute application modules.
154
+ - **SignalHeader centers its brand in the masthead** — `@voltro/ui-shadcn`
155
+
156
+ The `SignalHeader` brand slot is a centered flex row, so a brand link no longer sits on the text baseline and renders a few pixels above the masthead's center.
157
+ - **Update reports changed runtime patch assets before boot** — `@voltro/cli`
158
+
159
+ `voltro update` compares configured pnpm Effect and SQL-driver patches with the target CLI's assets during its codemod step, including `--codemods-only`. Changed bytes produce refresh and install instructions even without workflows. Same-version checks also report drift. Custom patch paths are named and files remain untouched.
160
+ - **Upgrade reviews omit locator counts and unchanged REST type plumbing** — `@voltro/cli`
161
+
162
+ The aggregate review excludes locator chains and local locator aliases while retaining uncertain query receivers. The idempotency review lists REST context constructions, context factories and guard definitions instead of every context or guard parameter annotation. Aliased imported calls in JavaScript custom hosts remain visible.
163
+
164
+ ### Internal (no consumer-facing effect)
165
+
166
+ - **Effect audits distinguish regression data from executable legacy APIs**
167
+
168
+ Effect migration audits allow test data to describe a foreign dependency's retained major. Removed package imports and obsolete bound API calls remain findings in tests and application code, while production migration-residue checks remain unchanged.
169
+ - **The doctor's table nullability manifest covers the billing history tables** — `@voltro/cli`
170
+
171
+ The generated nullability manifest `voltro doctor` reads was missing the invoice-history and customer-account tables the billing plugin added; it is regenerated from the declarations.
172
+ - **Installation checks refuse ambient workspaces and source overrides**
173
+
174
+ Installation checks require standalone directories before creating projects. Artifact consumers use shipped template and documentation assets without inheriting maintainer source overrides or Node module loaders. Registry, package-manager and explicit application settings remain available.
175
+ - **Installation checks require healthy applications and usable modules**
176
+
177
+ Installation checks require API readiness, successful web responses and transformed JavaScript modules while the development process remains running. HTTP errors and HTML fallbacks cannot satisfy those checks. Diagnostics distinguish application startup from shutdown.
178
+ - **Keep CLI fixture temporary roots and child outcomes explicit**
179
+
180
+ Automatic sidecar tests inspect the actual operating-system temporary directory and release their bound owner even when an assertion fails. Schema-boot fixtures retain the child's exit signal and assert the real exit tuple alongside readiness and migration counts, so a signal cannot become a false successful process result. Production security and signal guards remain unchanged.
181
+
182
+ Workflow recovery tests distinguish the recorded failure budget from concurrent dispatches already in flight. They retain the same prepared execution identity, require one body execution, and verify that stopped or accepted submissions cannot dispatch again.
183
+ - **Native SQL checks isolate schema ownership across fixtures**
184
+
185
+ Wallet and shop checks own separate server databases so concurrent schema creation cannot contend with another fixture's live writes. Independent pools within a fixture still share the real database. Cleanup closes all acquired pools before dropping only the owned namespace, and a native regression verifies isolation with identical wallet identities.
186
+ - **Native reload checks retain manifests published during SQL observation**
187
+
188
+ Native geometry checks establish the expected-version receiver before reload activation. A real transport regression holds the consumer until the new manifest arrives, so asynchronous SQL observation cannot hide a missed publication. Frame deadlines retain their original call sites.
189
+ - **Native snapshot probes join their scheduled driver**
190
+
191
+ Held-source stream probes quiesce and join the actual Host driver before directly pumping its captured graph. This prevents a scheduled turn from concurrently entering that graph and closing the fixture's native Session. Listener, SQL, controller, wire delivery, rights withdrawal and final cleanup assertions remain active; ordinary stream cases retain the running driver.
192
+ - **Bound the reviewed Sentry tool exception and retain every dependency instance**
193
+
194
+ The owner-reviewed exception accepts only sentry 0.45.0 under FSL-1.1-Apache-2.0 as unmodified external tooling for the Sentry integration. This does not classify FSL as permissive or remove its competing-use restriction. The runtime license walk checks every resolved instance, so an accepted version cannot hide a second version or license. Generated notices and the SBOM use actual package identities. Containment checks cover framework, workspace and scaffold patch files plus declared patches with arbitrary filenames; the API bundler leaves the tool external.
195
+ - **Stack scaffold checks require major-scoped runtime alignment**
196
+
197
+ The normal stack scaffold regression parses its generated workspace policy and verifies both Effect 4 selectors while refusing unqualified Effect and companion pins. Patch declaration and actual patch-byte checks remain, so the regression follows the preserved foreign-major contract instead of demanding its earlier unsafe global override. Its synthetic workspace declares its own pnpm version, making Compose baseline coverage independent of the test runner's package-manager environment.
198
+ - **Dependency security checks verify installed source remediations**
199
+
200
+ Dependency security checks accept a reviewed source remediation only after verifying exact patch and implementation hashes, patched references in every lockfile document, actual caller resolution and runtime behavior. Deepmerge's returned-object prototype protection preserves ordinary configuration merging. Unaffected dependency graphs receive no exception, and a local source remediation is never reported as an upstream fixed version.
201
+
202
+ ---
203
+
44
204
  ## [0.87.0] — 2026-10-31
45
205
 
46
206
  ### ⚠ BREAKING
@@ -3231,6 +3391,15 @@ _Changes staged for the next release accumulate here (rolled up from
3231
3391
  - **Prepare the exact XYFlow type correction before normal installation** — `@voltro/cli`
3232
3392
 
3233
3393
  `voltro add patches --xyflow 12.12.0` prepares the original XYFlow declaration correction and its complete license/notice before a normal package-manager or UI installation. Existing conflicting project patch assets are preserved and rejected before writes.
3394
+ - **Dispatchers drain accepted reads before store disposal** — `@voltro/runtime`, `@voltro/cli`
3395
+
3396
+ Runtime adds `Dispatcher.closeAndDrain()` to join accepted reads and deliveries before store disposal. Normal Dev and Serve API shutdown await it; synchronous `close()` remains available.
3397
+ - **Workflow cluster hosts declare shard groups and ClusterCron routing groups** — `@voltro/workflow`, `@voltro/cli`
3398
+
3399
+ Workflow cluster hosts can explicitly declare available/assigned shard groups and ClusterCron routing groups. Omitted settings retain existing routing; persistent journal migration is a separate prerequisite for changing groups.
3400
+ - **PostgreSQL workflow hosts can persist routing-generation admission** — `@voltro/workflow`, `@voltro/cli`
3401
+
3402
+ PostgreSQL workflow engine hosts can opt into persisted routing-generation admission with `journalRouting`; actual durable MessageStorage operations use the ownership guard. Full API-role wiring and maintenance rollout remain separate requirements.
3234
3403
 
3235
3404
  ### Changed
3236
3405
 
@@ -24321,9 +24490,3 @@ public registry yet.
24321
24490
 
24322
24491
  Subsequent releases record their deltas from here under dated headings, with
24323
24492
  `⚠ BREAKING` first.
24324
-
24325
- - Runtime adds `Dispatcher.closeAndDrain()` to join accepted reads and deliveries before store disposal. Normal Dev and Serve API shutdown await it; synchronous `close()` remains available.
24326
-
24327
- - Workflow cluster hosts can explicitly declare available/assigned shard groups and ClusterCron routing groups. Omitted settings retain existing routing; persistent journal migration is a separate prerequisite for changing groups.
24328
-
24329
- - PostgreSQL workflow engine hosts can opt into persisted routing-generation admission with `journalRouting`; actual durable MessageStorage operations use the ownership guard. Full API-role wiring and maintenance rollout remain separate requirements.
package/THIRD-PARTY-NOTICES.md CHANGED
@@ -1,15 +1,15 @@
1
1
  # Third-Party Notices — @voltro/plugin-moderation
2
2
 
3
- This package uses the open-source software listed below. Each is the
3
+ This package uses the third-party software listed below. Each is the
4
4
  property of its respective copyright holders and is used under the terms of
5
5
  its license. This file is provided for attribution; it grants no rights in
6
6
  @voltro/plugin-moderation itself, which is proprietary (see LICENSE).
7
7
 
8
- Generated from the resolved runtime dependency closure (58 packages).
8
+ Generated from the resolved runtime dependency closure (60 packages).
9
9
 
10
10
  ---
11
11
 
12
- ## @ai-sdk/anthropic@4.0.56
12
+ ## @ai-sdk/anthropic@4.0.91
13
13
 
14
14
  License: Apache-2.0
15
15
 
@@ -29,7 +29,7 @@ See the License for the specific language governing permissions and
29
29
  limitations under the License.
30
30
  ```
31
31
 
32
- ## @ai-sdk/openai@4.0.69
32
+ ## @ai-sdk/openai@4.0.104
33
33
 
34
34
  License: Apache-2.0
35
35
 
@@ -49,7 +49,7 @@ See the License for the specific language governing permissions and
49
49
  limitations under the License.
50
50
  ```
51
51
 
52
- ## @ai-sdk/provider@4.0.17
52
+ ## @ai-sdk/provider@4.0.34
53
53
 
54
54
  License: Apache-2.0
55
55
 
@@ -69,7 +69,7 @@ See the License for the specific language governing permissions and
69
69
  limitations under the License.
70
70
  ```
71
71
 
72
- ## @ai-sdk/provider-utils@5.0.43
72
+ ## @ai-sdk/provider-utils@5.0.70
73
73
 
74
74
  License: Apache-2.0
75
75
 
@@ -291,10 +291,10 @@ distributed under the License is distributed on an "AS IS" BASIS,
291
291
  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
292
292
  See the License for the specific language governing permissions and
293
293
  limitations under the License.
294
- Modified 2026-10-20: NeverOptional includes explicit undefined in the any branch for exactOptionalPropertyTypes. Declarations regenerated with the original tsup build; JavaScript and JavaScript source maps are unchanged.
294
+ Modified 2026-11-01: NeverOptional includes explicit undefined in the any branch for exactOptionalPropertyTypes. Declarations regenerated with the original tsdown build; JavaScript and JavaScript source maps are unchanged.
295
295
  ```
296
296
 
297
- ## @effect/platform-node@4.0.1
297
+ ## @effect/platform-node@4.1.0
298
298
 
299
299
  License: MIT
300
300
 
@@ -322,7 +322,7 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
322
322
  SOFTWARE.
323
323
  ```
324
324
 
325
- ## @effect/platform-node-shared@4.0.1
325
+ ## @effect/platform-node-shared@4.1.0
326
326
 
327
327
  License: MIT
328
328
 
@@ -350,7 +350,7 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
350
350
  SOFTWARE.
351
351
  ```
352
352
 
353
- ## @ioredis/commands@1.10.0
353
+ ## @ioredis/commands@2.0.0
354
354
 
355
355
  License: MIT
356
356
 
@@ -1627,7 +1627,7 @@ Apache License
1627
1627
  limitations under the License.
1628
1628
  ```
1629
1629
 
1630
- ## @opentelemetry/context-async-hooks@2.11.0
1630
+ ## @opentelemetry/context-async-hooks@2.12.0
1631
1631
 
1632
1632
  License: Apache-2.0
1633
1633
 
@@ -1835,7 +1835,7 @@ Apache License
1835
1835
  limitations under the License.
1836
1836
  ```
1837
1837
 
1838
- ## @opentelemetry/core@2.10.0
1838
+ ## @opentelemetry/core@2.12.0
1839
1839
 
1840
1840
  License: Apache-2.0
1841
1841
 
@@ -3083,6 +3083,214 @@ Apache License
3083
3083
  limitations under the License.
3084
3084
  ```
3085
3085
 
3086
+ ## @opentelemetry/resources@2.12.0
3087
+
3088
+ License: Apache-2.0
3089
+
3090
+ ```
3091
+ Apache License
3092
+ Version 2.0, January 2004
3093
+ http://www.apache.org/licenses/
3094
+
3095
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
3096
+
3097
+ 1. Definitions.
3098
+
3099
+ "License" shall mean the terms and conditions for use, reproduction,
3100
+ and distribution as defined by Sections 1 through 9 of this document.
3101
+
3102
+ "Licensor" shall mean the copyright owner or entity authorized by
3103
+ the copyright owner that is granting the License.
3104
+
3105
+ "Legal Entity" shall mean the union of the acting entity and all
3106
+ other entities that control, are controlled by, or are under common
3107
+ control with that entity. For the purposes of this definition,
3108
+ "control" means (i) the power, direct or indirect, to cause the
3109
+ direction or management of such entity, whether by contract or
3110
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
3111
+ outstanding shares, or (iii) beneficial ownership of such entity.
3112
+
3113
+ "You" (or "Your") shall mean an individual or Legal Entity
3114
+ exercising permissions granted by this License.
3115
+
3116
+ "Source" form shall mean the preferred form for making modifications,
3117
+ including but not limited to software source code, documentation
3118
+ source, and configuration files.
3119
+
3120
+ "Object" form shall mean any form resulting from mechanical
3121
+ transformation or translation of a Source form, including but
3122
+ not limited to compiled object code, generated documentation,
3123
+ and conversions to other media types.
3124
+
3125
+ "Work" shall mean the work of authorship, whether in Source or
3126
+ Object form, made available under the License, as indicated by a
3127
+ copyright notice that is included in or attached to the work
3128
+ (an example is provided in the Appendix below).
3129
+
3130
+ "Derivative Works" shall mean any work, whether in Source or Object
3131
+ form, that is based on (or derived from) the Work and for which the
3132
+ editorial revisions, annotations, elaborations, or other modifications
3133
+ represent, as a whole, an original work of authorship. For the purposes
3134
+ of this License, Derivative Works shall not include works that remain
3135
+ separable from, or merely link (or bind by name) to the interfaces of,
3136
+ the Work and Derivative Works thereof.
3137
+
3138
+ "Contribution" shall mean any work of authorship, including
3139
+ the original version of the Work and any modifications or additions
3140
+ to that Work or Derivative Works thereof, that is intentionally
3141
+ submitted to Licensor for inclusion in the Work by the copyright owner
3142
+ or by an individual or Legal Entity authorized to submit on behalf of
3143
+ the copyright owner. For the purposes of this definition, "submitted"
3144
+ means any form of electronic, verbal, or written communication sent
3145
+ to the Licensor or its representatives, including but not limited to
3146
+ communication on electronic mailing lists, source code control systems,
3147
+ and issue tracking systems that are managed by, or on behalf of, the
3148
+ Licensor for the purpose of discussing and improving the Work, but
3149
+ excluding communication that is conspicuously marked or otherwise
3150
+ designated in writing by the copyright owner as "Not a Contribution."
3151
+
3152
+ "Contributor" shall mean Licensor and any individual or Legal Entity
3153
+ on behalf of whom a Contribution has been received by Licensor and
3154
+ subsequently incorporated within the Work.
3155
+
3156
+ 2. Grant of Copyright License. Subject to the terms and conditions of
3157
+ this License, each Contributor hereby grants to You a perpetual,
3158
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
3159
+ copyright license to reproduce, prepare Derivative Works of,
3160
+ publicly display, publicly perform, sublicense, and distribute the
3161
+ Work and such Derivative Works in Source or Object form.
3162
+
3163
+ 3. Grant of Patent License. Subject to the terms and conditions of
3164
+ this License, each Contributor hereby grants to You a perpetual,
3165
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
3166
+ (except as stated in this section) patent license to make, have made,
3167
+ use, offer to sell, sell, import, and otherwise transfer the Work,
3168
+ where such license applies only to those patent claims licensable
3169
+ by such Contributor that are necessarily infringed by their
3170
+ Contribution(s) alone or by combination of their Contribution(s)
3171
+ with the Work to which such Contribution(s) was submitted. If You
3172
+ institute patent litigation against any entity (including a
3173
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
3174
+ or a Contribution incorporated within the Work constitutes direct
3175
+ or contributory patent infringement, then any patent licenses
3176
+ granted to You under this License for that Work shall terminate
3177
+ as of the date such litigation is filed.
3178
+
3179
+ 4. Redistribution. You may reproduce and distribute copies of the
3180
+ Work or Derivative Works thereof in any medium, with or without
3181
+ modifications, and in Source or Object form, provided that You
3182
+ meet the following conditions:
3183
+
3184
+ (a) You must give any other recipients of the Work or
3185
+ Derivative Works a copy of this License; and
3186
+
3187
+ (b) You must cause any modified files to carry prominent notices
3188
+ stating that You changed the files; and
3189
+
3190
+ (c) You must retain, in the Source form of any Derivative Works
3191
+ that You distribute, all copyright, patent, trademark, and
3192
+ attribution notices from the Source form of the Work,
3193
+ excluding those notices that do not pertain to any part of
3194
+ the Derivative Works; and
3195
+
3196
+ (d) If the Work includes a "NOTICE" text file as part of its
3197
+ distribution, then any Derivative Works that You distribute must
3198
+ include a readable copy of the attribution notices contained
3199
+ within such NOTICE file, excluding those notices that do not
3200
+ pertain to any part of the Derivative Works, in at least one
3201
+ of the following places: within a NOTICE text file distributed
3202
+ as part of the Derivative Works; within the Source form or
3203
+ documentation, if provided along with the Derivative Works; or,
3204
+ within a display generated by the Derivative Works, if and
3205
+ wherever such third-party notices normally appear. The contents
3206
+ of the NOTICE file are for informational purposes only and
3207
+ do not modify the License. You may add Your own attribution
3208
+ notices within Derivative Works that You distribute, alongside
3209
+ or as an addendum to the NOTICE text from the Work, provided
3210
+ that such additional attribution notices cannot be construed
3211
+ as modifying the License.
3212
+
3213
+ You may add Your own copyright statement to Your modifications and
3214
+ may provide additional or different license terms and conditions
3215
+ for use, reproduction, or distribution of Your modifications, or
3216
+ for any such Derivative Works as a whole, provided Your use,
3217
+ reproduction, and distribution of the Work otherwise complies with
3218
+ the conditions stated in this License.
3219
+
3220
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
3221
+ any Contribution intentionally submitted for inclusion in the Work
3222
+ by You to the Licensor shall be under the terms and conditions of
3223
+ this License, without any additional terms or conditions.
3224
+ Notwithstanding the above, nothing herein shall supersede or modify
3225
+ the terms of any separate license agreement you may have executed
3226
+ with Licensor regarding such Contributions.
3227
+
3228
+ 6. Trademarks. This License does not grant permission to use the trade
3229
+ names, trademarks, service marks, or product names of the Licensor,
3230
+ except as required for reasonable and customary use in describing the
3231
+ origin of the Work and reproducing the content of the NOTICE file.
3232
+
3233
+ 7. Disclaimer of Warranty. Unless required by applicable law or
3234
+ agreed to in writing, Licensor provides the Work (and each
3235
+ Contributor provides its Contributions) on an "AS IS" BASIS,
3236
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
3237
+ implied, including, without limitation, any warranties or conditions
3238
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
3239
+ PARTICULAR PURPOSE. You are solely responsible for determining the
3240
+ appropriateness of using or redistributing the Work and assume any
3241
+ risks associated with Your exercise of permissions under this License.
3242
+
3243
+ 8. Limitation of Liability. In no event and under no legal theory,
3244
+ whether in tort (including negligence), contract, or otherwise,
3245
+ unless required by applicable law (such as deliberate and grossly
3246
+ negligent acts) or agreed to in writing, shall any Contributor be
3247
+ liable to You for damages, including any direct, indirect, special,
3248
+ incidental, or consequential damages of any character arising as a
3249
+ result of this License or out of the use or inability to use the
3250
+ Work (including but not limited to damages for loss of goodwill,
3251
+ work stoppage, computer failure or malfunction, or any and all
3252
+ other commercial damages or losses), even if such Contributor
3253
+ has been advised of the possibility of such damages.
3254
+
3255
+ 9. Accepting Warranty or Additional Liability. While redistributing
3256
+ the Work or Derivative Works thereof, You may choose to offer,
3257
+ and charge a fee for, acceptance of support, warranty, indemnity,
3258
+ or other liability obligations and/or rights consistent with this
3259
+ License. However, in accepting such obligations, You may act only
3260
+ on Your own behalf and on Your sole responsibility, not on behalf
3261
+ of any other Contributor, and only if You agree to indemnify,
3262
+ defend, and hold each Contributor harmless for any liability
3263
+ incurred by, or claims asserted against, such Contributor by reason
3264
+ of your accepting any such warranty or additional liability.
3265
+
3266
+ END OF TERMS AND CONDITIONS
3267
+
3268
+ APPENDIX: How to apply the Apache License to your work.
3269
+
3270
+ To apply the Apache License to your work, attach the following
3271
+ boilerplate notice, with the fields enclosed by brackets "[]"
3272
+ replaced with your own identifying information. (Don't include
3273
+ the brackets!) The text should be enclosed in the appropriate
3274
+ comment syntax for the file format. We also recommend that a
3275
+ file or class name and description of purpose be included on the
3276
+ same "printed page" as the copyright notice for easier
3277
+ identification within third-party archives.
3278
+
3279
+ Copyright [yyyy] [name of copyright owner]
3280
+
3281
+ Licensed under the Apache License, Version 2.0 (the "License");
3282
+ you may not use this file except in compliance with the License.
3283
+ You may obtain a copy of the License at
3284
+
3285
+ http://www.apache.org/licenses/LICENSE-2.0
3286
+
3287
+ Unless required by applicable law or agreed to in writing, software
3288
+ distributed under the License is distributed on an "AS IS" BASIS,
3289
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
3290
+ See the License for the specific language governing permissions and
3291
+ limitations under the License.
3292
+ ```
3293
+
3086
3294
  ## @opentelemetry/sdk-logs@0.222.0
3087
3295
 
3088
3296
  License: Apache-2.0
@@ -3291,7 +3499,215 @@ Apache License
3291
3499
  limitations under the License.
3292
3500
  ```
3293
3501
 
3294
- ## @opentelemetry/sdk-metrics@2.11.0
3502
+ ## @opentelemetry/sdk-metrics@2.11.0
3503
+
3504
+ License: Apache-2.0
3505
+
3506
+ ```
3507
+ Apache License
3508
+ Version 2.0, January 2004
3509
+ http://www.apache.org/licenses/
3510
+
3511
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
3512
+
3513
+ 1. Definitions.
3514
+
3515
+ "License" shall mean the terms and conditions for use, reproduction,
3516
+ and distribution as defined by Sections 1 through 9 of this document.
3517
+
3518
+ "Licensor" shall mean the copyright owner or entity authorized by
3519
+ the copyright owner that is granting the License.
3520
+
3521
+ "Legal Entity" shall mean the union of the acting entity and all
3522
+ other entities that control, are controlled by, or are under common
3523
+ control with that entity. For the purposes of this definition,
3524
+ "control" means (i) the power, direct or indirect, to cause the
3525
+ direction or management of such entity, whether by contract or
3526
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
3527
+ outstanding shares, or (iii) beneficial ownership of such entity.
3528
+
3529
+ "You" (or "Your") shall mean an individual or Legal Entity
3530
+ exercising permissions granted by this License.
3531
+
3532
+ "Source" form shall mean the preferred form for making modifications,
3533
+ including but not limited to software source code, documentation
3534
+ source, and configuration files.
3535
+
3536
+ "Object" form shall mean any form resulting from mechanical
3537
+ transformation or translation of a Source form, including but
3538
+ not limited to compiled object code, generated documentation,
3539
+ and conversions to other media types.
3540
+
3541
+ "Work" shall mean the work of authorship, whether in Source or
3542
+ Object form, made available under the License, as indicated by a
3543
+ copyright notice that is included in or attached to the work
3544
+ (an example is provided in the Appendix below).
3545
+
3546
+ "Derivative Works" shall mean any work, whether in Source or Object
3547
+ form, that is based on (or derived from) the Work and for which the
3548
+ editorial revisions, annotations, elaborations, or other modifications
3549
+ represent, as a whole, an original work of authorship. For the purposes
3550
+ of this License, Derivative Works shall not include works that remain
3551
+ separable from, or merely link (or bind by name) to the interfaces of,
3552
+ the Work and Derivative Works thereof.
3553
+
3554
+ "Contribution" shall mean any work of authorship, including
3555
+ the original version of the Work and any modifications or additions
3556
+ to that Work or Derivative Works thereof, that is intentionally
3557
+ submitted to Licensor for inclusion in the Work by the copyright owner
3558
+ or by an individual or Legal Entity authorized to submit on behalf of
3559
+ the copyright owner. For the purposes of this definition, "submitted"
3560
+ means any form of electronic, verbal, or written communication sent
3561
+ to the Licensor or its representatives, including but not limited to
3562
+ communication on electronic mailing lists, source code control systems,
3563
+ and issue tracking systems that are managed by, or on behalf of, the
3564
+ Licensor for the purpose of discussing and improving the Work, but
3565
+ excluding communication that is conspicuously marked or otherwise
3566
+ designated in writing by the copyright owner as "Not a Contribution."
3567
+
3568
+ "Contributor" shall mean Licensor and any individual or Legal Entity
3569
+ on behalf of whom a Contribution has been received by Licensor and
3570
+ subsequently incorporated within the Work.
3571
+
3572
+ 2. Grant of Copyright License. Subject to the terms and conditions of
3573
+ this License, each Contributor hereby grants to You a perpetual,
3574
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
3575
+ copyright license to reproduce, prepare Derivative Works of,
3576
+ publicly display, publicly perform, sublicense, and distribute the
3577
+ Work and such Derivative Works in Source or Object form.
3578
+
3579
+ 3. Grant of Patent License. Subject to the terms and conditions of
3580
+ this License, each Contributor hereby grants to You a perpetual,
3581
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
3582
+ (except as stated in this section) patent license to make, have made,
3583
+ use, offer to sell, sell, import, and otherwise transfer the Work,
3584
+ where such license applies only to those patent claims licensable
3585
+ by such Contributor that are necessarily infringed by their
3586
+ Contribution(s) alone or by combination of their Contribution(s)
3587
+ with the Work to which such Contribution(s) was submitted. If You
3588
+ institute patent litigation against any entity (including a
3589
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
3590
+ or a Contribution incorporated within the Work constitutes direct
3591
+ or contributory patent infringement, then any patent licenses
3592
+ granted to You under this License for that Work shall terminate
3593
+ as of the date such litigation is filed.
3594
+
3595
+ 4. Redistribution. You may reproduce and distribute copies of the
3596
+ Work or Derivative Works thereof in any medium, with or without
3597
+ modifications, and in Source or Object form, provided that You
3598
+ meet the following conditions:
3599
+
3600
+ (a) You must give any other recipients of the Work or
3601
+ Derivative Works a copy of this License; and
3602
+
3603
+ (b) You must cause any modified files to carry prominent notices
3604
+ stating that You changed the files; and
3605
+
3606
+ (c) You must retain, in the Source form of any Derivative Works
3607
+ that You distribute, all copyright, patent, trademark, and
3608
+ attribution notices from the Source form of the Work,
3609
+ excluding those notices that do not pertain to any part of
3610
+ the Derivative Works; and
3611
+
3612
+ (d) If the Work includes a "NOTICE" text file as part of its
3613
+ distribution, then any Derivative Works that You distribute must
3614
+ include a readable copy of the attribution notices contained
3615
+ within such NOTICE file, excluding those notices that do not
3616
+ pertain to any part of the Derivative Works, in at least one
3617
+ of the following places: within a NOTICE text file distributed
3618
+ as part of the Derivative Works; within the Source form or
3619
+ documentation, if provided along with the Derivative Works; or,
3620
+ within a display generated by the Derivative Works, if and
3621
+ wherever such third-party notices normally appear. The contents
3622
+ of the NOTICE file are for informational purposes only and
3623
+ do not modify the License. You may add Your own attribution
3624
+ notices within Derivative Works that You distribute, alongside
3625
+ or as an addendum to the NOTICE text from the Work, provided
3626
+ that such additional attribution notices cannot be construed
3627
+ as modifying the License.
3628
+
3629
+ You may add Your own copyright statement to Your modifications and
3630
+ may provide additional or different license terms and conditions
3631
+ for use, reproduction, or distribution of Your modifications, or
3632
+ for any such Derivative Works as a whole, provided Your use,
3633
+ reproduction, and distribution of the Work otherwise complies with
3634
+ the conditions stated in this License.
3635
+
3636
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
3637
+ any Contribution intentionally submitted for inclusion in the Work
3638
+ by You to the Licensor shall be under the terms and conditions of
3639
+ this License, without any additional terms or conditions.
3640
+ Notwithstanding the above, nothing herein shall supersede or modify
3641
+ the terms of any separate license agreement you may have executed
3642
+ with Licensor regarding such Contributions.
3643
+
3644
+ 6. Trademarks. This License does not grant permission to use the trade
3645
+ names, trademarks, service marks, or product names of the Licensor,
3646
+ except as required for reasonable and customary use in describing the
3647
+ origin of the Work and reproducing the content of the NOTICE file.
3648
+
3649
+ 7. Disclaimer of Warranty. Unless required by applicable law or
3650
+ agreed to in writing, Licensor provides the Work (and each
3651
+ Contributor provides its Contributions) on an "AS IS" BASIS,
3652
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
3653
+ implied, including, without limitation, any warranties or conditions
3654
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
3655
+ PARTICULAR PURPOSE. You are solely responsible for determining the
3656
+ appropriateness of using or redistributing the Work and assume any
3657
+ risks associated with Your exercise of permissions under this License.
3658
+
3659
+ 8. Limitation of Liability. In no event and under no legal theory,
3660
+ whether in tort (including negligence), contract, or otherwise,
3661
+ unless required by applicable law (such as deliberate and grossly
3662
+ negligent acts) or agreed to in writing, shall any Contributor be
3663
+ liable to You for damages, including any direct, indirect, special,
3664
+ incidental, or consequential damages of any character arising as a
3665
+ result of this License or out of the use or inability to use the
3666
+ Work (including but not limited to damages for loss of goodwill,
3667
+ work stoppage, computer failure or malfunction, or any and all
3668
+ other commercial damages or losses), even if such Contributor
3669
+ has been advised of the possibility of such damages.
3670
+
3671
+ 9. Accepting Warranty or Additional Liability. While redistributing
3672
+ the Work or Derivative Works thereof, You may choose to offer,
3673
+ and charge a fee for, acceptance of support, warranty, indemnity,
3674
+ or other liability obligations and/or rights consistent with this
3675
+ License. However, in accepting such obligations, You may act only
3676
+ on Your own behalf and on Your sole responsibility, not on behalf
3677
+ of any other Contributor, and only if You agree to indemnify,
3678
+ defend, and hold each Contributor harmless for any liability
3679
+ incurred by, or claims asserted against, such Contributor by reason
3680
+ of your accepting any such warranty or additional liability.
3681
+
3682
+ END OF TERMS AND CONDITIONS
3683
+
3684
+ APPENDIX: How to apply the Apache License to your work.
3685
+
3686
+ To apply the Apache License to your work, attach the following
3687
+ boilerplate notice, with the fields enclosed by brackets "[]"
3688
+ replaced with your own identifying information. (Don't include
3689
+ the brackets!) The text should be enclosed in the appropriate
3690
+ comment syntax for the file format. We also recommend that a
3691
+ file or class name and description of purpose be included on the
3692
+ same "printed page" as the copyright notice for easier
3693
+ identification within third-party archives.
3694
+
3695
+ Copyright [yyyy] [name of copyright owner]
3696
+
3697
+ Licensed under the Apache License, Version 2.0 (the "License");
3698
+ you may not use this file except in compliance with the License.
3699
+ You may obtain a copy of the License at
3700
+
3701
+ http://www.apache.org/licenses/LICENSE-2.0
3702
+
3703
+ Unless required by applicable law or agreed to in writing, software
3704
+ distributed under the License is distributed on an "AS IS" BASIS,
3705
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
3706
+ See the License for the specific language governing permissions and
3707
+ limitations under the License.
3708
+ ```
3709
+
3710
+ ## @opentelemetry/sdk-metrics@2.12.0
3295
3711
 
3296
3712
  License: Apache-2.0
3297
3713
 
@@ -3707,7 +4123,215 @@ Apache License
3707
4123
  limitations under the License.
3708
4124
  ```
3709
4125
 
3710
- ## @opentelemetry/sdk-trace-base@2.11.0
4126
+ ## @opentelemetry/sdk-trace@2.12.0
4127
+
4128
+ License: Apache-2.0
4129
+
4130
+ ```
4131
+ Apache License
4132
+ Version 2.0, January 2004
4133
+ http://www.apache.org/licenses/
4134
+
4135
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
4136
+
4137
+ 1. Definitions.
4138
+
4139
+ "License" shall mean the terms and conditions for use, reproduction,
4140
+ and distribution as defined by Sections 1 through 9 of this document.
4141
+
4142
+ "Licensor" shall mean the copyright owner or entity authorized by
4143
+ the copyright owner that is granting the License.
4144
+
4145
+ "Legal Entity" shall mean the union of the acting entity and all
4146
+ other entities that control, are controlled by, or are under common
4147
+ control with that entity. For the purposes of this definition,
4148
+ "control" means (i) the power, direct or indirect, to cause the
4149
+ direction or management of such entity, whether by contract or
4150
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
4151
+ outstanding shares, or (iii) beneficial ownership of such entity.
4152
+
4153
+ "You" (or "Your") shall mean an individual or Legal Entity
4154
+ exercising permissions granted by this License.
4155
+
4156
+ "Source" form shall mean the preferred form for making modifications,
4157
+ including but not limited to software source code, documentation
4158
+ source, and configuration files.
4159
+
4160
+ "Object" form shall mean any form resulting from mechanical
4161
+ transformation or translation of a Source form, including but
4162
+ not limited to compiled object code, generated documentation,
4163
+ and conversions to other media types.
4164
+
4165
+ "Work" shall mean the work of authorship, whether in Source or
4166
+ Object form, made available under the License, as indicated by a
4167
+ copyright notice that is included in or attached to the work
4168
+ (an example is provided in the Appendix below).
4169
+
4170
+ "Derivative Works" shall mean any work, whether in Source or Object
4171
+ form, that is based on (or derived from) the Work and for which the
4172
+ editorial revisions, annotations, elaborations, or other modifications
4173
+ represent, as a whole, an original work of authorship. For the purposes
4174
+ of this License, Derivative Works shall not include works that remain
4175
+ separable from, or merely link (or bind by name) to the interfaces of,
4176
+ the Work and Derivative Works thereof.
4177
+
4178
+ "Contribution" shall mean any work of authorship, including
4179
+ the original version of the Work and any modifications or additions
4180
+ to that Work or Derivative Works thereof, that is intentionally
4181
+ submitted to Licensor for inclusion in the Work by the copyright owner
4182
+ or by an individual or Legal Entity authorized to submit on behalf of
4183
+ the copyright owner. For the purposes of this definition, "submitted"
4184
+ means any form of electronic, verbal, or written communication sent
4185
+ to the Licensor or its representatives, including but not limited to
4186
+ communication on electronic mailing lists, source code control systems,
4187
+ and issue tracking systems that are managed by, or on behalf of, the
4188
+ Licensor for the purpose of discussing and improving the Work, but
4189
+ excluding communication that is conspicuously marked or otherwise
4190
+ designated in writing by the copyright owner as "Not a Contribution."
4191
+
4192
+ "Contributor" shall mean Licensor and any individual or Legal Entity
4193
+ on behalf of whom a Contribution has been received by Licensor and
4194
+ subsequently incorporated within the Work.
4195
+
4196
+ 2. Grant of Copyright License. Subject to the terms and conditions of
4197
+ this License, each Contributor hereby grants to You a perpetual,
4198
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
4199
+ copyright license to reproduce, prepare Derivative Works of,
4200
+ publicly display, publicly perform, sublicense, and distribute the
4201
+ Work and such Derivative Works in Source or Object form.
4202
+
4203
+ 3. Grant of Patent License. Subject to the terms and conditions of
4204
+ this License, each Contributor hereby grants to You a perpetual,
4205
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
4206
+ (except as stated in this section) patent license to make, have made,
4207
+ use, offer to sell, sell, import, and otherwise transfer the Work,
4208
+ where such license applies only to those patent claims licensable
4209
+ by such Contributor that are necessarily infringed by their
4210
+ Contribution(s) alone or by combination of their Contribution(s)
4211
+ with the Work to which such Contribution(s) was submitted. If You
4212
+ institute patent litigation against any entity (including a
4213
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
4214
+ or a Contribution incorporated within the Work constitutes direct
4215
+ or contributory patent infringement, then any patent licenses
4216
+ granted to You under this License for that Work shall terminate
4217
+ as of the date such litigation is filed.
4218
+
4219
+ 4. Redistribution. You may reproduce and distribute copies of the
4220
+ Work or Derivative Works thereof in any medium, with or without
4221
+ modifications, and in Source or Object form, provided that You
4222
+ meet the following conditions:
4223
+
4224
+ (a) You must give any other recipients of the Work or
4225
+ Derivative Works a copy of this License; and
4226
+
4227
+ (b) You must cause any modified files to carry prominent notices
4228
+ stating that You changed the files; and
4229
+
4230
+ (c) You must retain, in the Source form of any Derivative Works
4231
+ that You distribute, all copyright, patent, trademark, and
4232
+ attribution notices from the Source form of the Work,
4233
+ excluding those notices that do not pertain to any part of
4234
+ the Derivative Works; and
4235
+
4236
+ (d) If the Work includes a "NOTICE" text file as part of its
4237
+ distribution, then any Derivative Works that You distribute must
4238
+ include a readable copy of the attribution notices contained
4239
+ within such NOTICE file, excluding those notices that do not
4240
+ pertain to any part of the Derivative Works, in at least one
4241
+ of the following places: within a NOTICE text file distributed
4242
+ as part of the Derivative Works; within the Source form or
4243
+ documentation, if provided along with the Derivative Works; or,
4244
+ within a display generated by the Derivative Works, if and
4245
+ wherever such third-party notices normally appear. The contents
4246
+ of the NOTICE file are for informational purposes only and
4247
+ do not modify the License. You may add Your own attribution
4248
+ notices within Derivative Works that You distribute, alongside
4249
+ or as an addendum to the NOTICE text from the Work, provided
4250
+ that such additional attribution notices cannot be construed
4251
+ as modifying the License.
4252
+
4253
+ You may add Your own copyright statement to Your modifications and
4254
+ may provide additional or different license terms and conditions
4255
+ for use, reproduction, or distribution of Your modifications, or
4256
+ for any such Derivative Works as a whole, provided Your use,
4257
+ reproduction, and distribution of the Work otherwise complies with
4258
+ the conditions stated in this License.
4259
+
4260
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
4261
+ any Contribution intentionally submitted for inclusion in the Work
4262
+ by You to the Licensor shall be under the terms and conditions of
4263
+ this License, without any additional terms or conditions.
4264
+ Notwithstanding the above, nothing herein shall supersede or modify
4265
+ the terms of any separate license agreement you may have executed
4266
+ with Licensor regarding such Contributions.
4267
+
4268
+ 6. Trademarks. This License does not grant permission to use the trade
4269
+ names, trademarks, service marks, or product names of the Licensor,
4270
+ except as required for reasonable and customary use in describing the
4271
+ origin of the Work and reproducing the content of the NOTICE file.
4272
+
4273
+ 7. Disclaimer of Warranty. Unless required by applicable law or
4274
+ agreed to in writing, Licensor provides the Work (and each
4275
+ Contributor provides its Contributions) on an "AS IS" BASIS,
4276
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
4277
+ implied, including, without limitation, any warranties or conditions
4278
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
4279
+ PARTICULAR PURPOSE. You are solely responsible for determining the
4280
+ appropriateness of using or redistributing the Work and assume any
4281
+ risks associated with Your exercise of permissions under this License.
4282
+
4283
+ 8. Limitation of Liability. In no event and under no legal theory,
4284
+ whether in tort (including negligence), contract, or otherwise,
4285
+ unless required by applicable law (such as deliberate and grossly
4286
+ negligent acts) or agreed to in writing, shall any Contributor be
4287
+ liable to You for damages, including any direct, indirect, special,
4288
+ incidental, or consequential damages of any character arising as a
4289
+ result of this License or out of the use or inability to use the
4290
+ Work (including but not limited to damages for loss of goodwill,
4291
+ work stoppage, computer failure or malfunction, or any and all
4292
+ other commercial damages or losses), even if such Contributor
4293
+ has been advised of the possibility of such damages.
4294
+
4295
+ 9. Accepting Warranty or Additional Liability. While redistributing
4296
+ the Work or Derivative Works thereof, You may choose to offer,
4297
+ and charge a fee for, acceptance of support, warranty, indemnity,
4298
+ or other liability obligations and/or rights consistent with this
4299
+ License. However, in accepting such obligations, You may act only
4300
+ on Your own behalf and on Your sole responsibility, not on behalf
4301
+ of any other Contributor, and only if You agree to indemnify,
4302
+ defend, and hold each Contributor harmless for any liability
4303
+ incurred by, or claims asserted against, such Contributor by reason
4304
+ of your accepting any such warranty or additional liability.
4305
+
4306
+ END OF TERMS AND CONDITIONS
4307
+
4308
+ APPENDIX: How to apply the Apache License to your work.
4309
+
4310
+ To apply the Apache License to your work, attach the following
4311
+ boilerplate notice, with the fields enclosed by brackets "[]"
4312
+ replaced with your own identifying information. (Don't include
4313
+ the brackets!) The text should be enclosed in the appropriate
4314
+ comment syntax for the file format. We also recommend that a
4315
+ file or class name and description of purpose be included on the
4316
+ same "printed page" as the copyright notice for easier
4317
+ identification within third-party archives.
4318
+
4319
+ Copyright [yyyy] [name of copyright owner]
4320
+
4321
+ Licensed under the Apache License, Version 2.0 (the "License");
4322
+ you may not use this file except in compliance with the License.
4323
+ You may obtain a copy of the License at
4324
+
4325
+ http://www.apache.org/licenses/LICENSE-2.0
4326
+
4327
+ Unless required by applicable law or agreed to in writing, software
4328
+ distributed under the License is distributed on an "AS IS" BASIS,
4329
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
4330
+ See the License for the specific language governing permissions and
4331
+ limitations under the License.
4332
+ ```
4333
+
4334
+ ## @opentelemetry/sdk-trace-base@2.12.0
3711
4335
 
3712
4336
  License: Apache-2.0
3713
4337
 
@@ -3915,7 +4539,7 @@ Apache License
3915
4539
  limitations under the License.
3916
4540
  ```
3917
4541
 
3918
- ## @opentelemetry/sdk-trace-node@2.11.0
4542
+ ## @opentelemetry/sdk-trace-node@2.12.0
3919
4543
 
3920
4544
  License: Apache-2.0
3921
4545
 
@@ -4123,7 +4747,7 @@ Apache License
4123
4747
  limitations under the License.
4124
4748
  ```
4125
4749
 
4126
- ## @opentelemetry/semantic-conventions@1.43.0
4750
+ ## @opentelemetry/semantic-conventions@1.44.0
4127
4751
 
4128
4752
  License: Apache-2.0
4129
4753
 
@@ -4359,7 +4983,7 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
4359
4983
  SOFTWARE.
4360
4984
  ```
4361
4985
 
4362
- ## @types/node@26.4.1
4986
+ ## @types/node@26.6.6
4363
4987
 
4364
4988
  License: MIT
4365
4989
 
@@ -4387,7 +5011,7 @@ MIT License
4387
5011
  SOFTWARE
4388
5012
  ```
4389
5013
 
4390
- ## @types/ws@8.18.1
5014
+ ## @types/ws@8.18.2
4391
5015
 
4392
5016
  License: MIT
4393
5017
 
@@ -4415,7 +5039,7 @@ MIT License
4415
5039
  SOFTWARE
4416
5040
  ```
4417
5041
 
4418
- ## @upstash/redis@1.38.4
5042
+ ## @upstash/redis@1.40.0
4419
5043
 
4420
5044
  License: MIT
4421
5045
 
@@ -4856,7 +5480,7 @@ The complete list of contributors can be found at:
4856
5480
  - https://github.com/garycourt/uri-js/graphs/contributors
4857
5481
  ```
4858
5482
 
4859
- ## ioredis@5.11.1
5483
+ ## ioredis@6.0.0
4860
5484
 
4861
5485
  License: MIT
4862
5486
 
@@ -4912,7 +5536,7 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
4912
5536
  SOFTWARE.
4913
5537
  ```
4914
5538
 
4915
- ## jose@6.2.12
5539
+ ## jose@6.2.13
4916
5540
 
4917
5541
  License: MIT
4918
5542
 
@@ -5170,7 +5794,7 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
5170
5794
  SOFTWARE.
5171
5795
  ```
5172
5796
 
5173
- ## lib0@0.2.117
5797
+ ## lib0@0.2.119
5174
5798
 
5175
5799
  License: MIT
5176
5800
 
@@ -5254,34 +5878,6 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
5254
5878
  SOFTWARE.
5255
5879
  ```
5256
5880
 
5257
- ## redis-parser@3.0.0
5258
-
5259
- License: MIT
5260
-
5261
- ```
5262
- The MIT License (MIT)
5263
-
5264
- Copyright (c) 2015 NodeRedis
5265
-
5266
- Permission is hereby granted, free of charge, to any person obtaining a copy
5267
- of this software and associated documentation files (the "Software"), to deal
5268
- in the Software without restriction, including without limitation the rights
5269
- to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
5270
- copies of the Software, and to permit persons to whom the Software is
5271
- furnished to do so, subject to the following conditions:
5272
-
5273
- The above copyright notice and this permission notice shall be included in all
5274
- copies or substantial portions of the Software.
5275
-
5276
- THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
5277
- IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
5278
- FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
5279
- AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
5280
- LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
5281
- OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
5282
- SOFTWARE.
5283
- ```
5284
-
5285
5881
  ## require-from-string@2.0.2
5286
5882
 
5287
5883
  License: MIT
@@ -5454,7 +6050,7 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
5454
6050
  SOFTWARE.
5455
6051
  ```
5456
6052
 
5457
- ## undici-types@8.3.0
6053
+ ## undici-types@8.9.0
5458
6054
 
5459
6055
  License: MIT
5460
6056
 
@@ -5482,7 +6078,7 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
5482
6078
  SOFTWARE.
5483
6079
  ```
5484
6080
 
5485
- ## ws@8.21.0
6081
+ ## ws@8.22.0
5486
6082
 
5487
6083
  License: MIT
5488
6084
 
@@ -5537,7 +6133,7 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
5537
6133
  SOFTWARE.
5538
6134
  ```
5539
6135
 
5540
- ## yjs@13.6.32
6136
+ ## yjs@13.6.33
5541
6137
 
5542
6138
  License: MIT
5543
6139
 
package/dist/errors.js CHANGED
@@ -1,9 +1,8 @@
1
1
  import { Schema as e } from "effect";
2
- //#region src/errors.ts
2
+ // src/errors.ts
3
3
  var t = class extends e.TaggedError()("ContentRejected", {
4
4
  tag: e.String,
5
5
  categories: e.Array(e.String),
6
6
  reason: e.String
7
7
  }) {};
8
- //#endregion
9
8
  export { t as ContentRejected };
package/dist/index.js CHANGED
@@ -2,7 +2,7 @@ import { ContentRejected as e } from "./errors.js";
2
2
  import { aiProvider as t, keywordProvider as n } from "./providers.js";
3
3
  import { Context as r, Effect as i, Layer as a } from "effect";
4
4
  import { definePlugin as o, pluginInstanceName as s } from "@voltro/protocol";
5
- //#region src/index.ts
5
+ // src/index.ts
6
6
  var c = class extends r.Service()("@voltro/plugin-moderation/ModerationService") {}, l = (e) => i.flatMap(c, (t) => t.moderate(e)), u = (e, t) => {
7
7
  if (typeof e != "object" || !e) return "";
8
8
  let n = e;
@@ -122,5 +122,4 @@ var c = class extends r.Service()("@voltro/plugin-moderation/ModerationService")
122
122
  })
123
123
  });
124
124
  };
125
- //#endregion
126
125
  export { e as ContentRejected, c as ModerationService, t as aiProvider, n as keywordProvider, l as moderate, f as moderationPlugin };
package/dist/providers.js CHANGED
@@ -1,6 +1,6 @@
1
1
  import { Effect as e } from "effect";
2
2
  import { createLogger as t } from "@voltro/logger";
3
- //#region src/providers.ts
3
+ // src/providers.ts
4
4
  var n = t({ scope: "@voltro/plugin-moderation" }), r = { flagged: !1 }, i = /[.*+?^${}()|[\]\\]/g, a = (e) => {
5
5
  let t = (e) => e !== void 0 && /[\p{L}\p{N}_]/u.test(e), n = t(e[0]) ? "\\b" : "", r = t(e[e.length - 1]) ? "\\b" : "";
6
6
  return RegExp(`${n}${e.replace(i, "\\$&")}${r}`, "u");
@@ -47,5 +47,4 @@ var n = t({ scope: "@voltro/plugin-moderation" }), r = { flagged: !1 }, i = /[.*
47
47
  }).pipe(e.catch(() => e.succeed(r)));
48
48
  });
49
49
  };
50
- //#endregion
51
50
  export { s as aiProvider, o as keywordProvider };
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@voltro/plugin-moderation",
3
- "version": "0.87.0",
3
+ "version": "0.88.0",
4
4
  "description": "Content moderation — run an AI / keyword / custom check on user-content fields and block or flag a write before it commits. Declarative per-rpc rules + an in-handler moderate() helper for redact/inline control.",
5
5
  "keywords": [
6
6
  "voltro",
@@ -38,14 +38,14 @@
38
38
  "node": ">=24.0.0"
39
39
  },
40
40
  "dependencies": {
41
- "@voltro/logger": "0.87.0",
42
- "@voltro/protocol": "0.87.0"
41
+ "@voltro/logger": "0.88.0",
42
+ "@voltro/protocol": "0.88.0"
43
43
  },
44
44
  "optionalDependencies": {
45
- "@voltro/ai": "0.87.0"
45
+ "@voltro/ai": "0.88.0"
46
46
  },
47
47
  "peerDependencies": {
48
- "effect": "4.0.1"
48
+ "effect": "4.1.0"
49
49
  },
50
50
  "publishConfig": {
51
51
  "access": "public"