@voltro/plugin-clickhouse 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 (5) hide show
  1. package/CHANGELOG.md +169 -6
  2. package/THIRD-PARTY-NOTICES.md +645 -49
  3. package/dist/index.js +1 -2
  4. package/dist/sink.js +1 -2
  5. 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-clickhouse
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-clickhouse itself, which is proprietary (see LICENSE).
7
7
 
8
- Generated from the resolved runtime dependency closure (45 packages).
8
+ Generated from the resolved runtime dependency closure (47 packages).
9
9
 
10
10
  ---
11
11
 
12
- ## @clickhouse/client@1.23.1
12
+ ## @clickhouse/client@1.24.1
13
13
 
14
14
  License: Apache-2.0
15
15
 
@@ -219,7 +219,7 @@ Copyright 2016-2024 ClickHouse, Inc.
219
219
  limitations under the License.
220
220
  ```
221
221
 
222
- ## @effect/platform-node@4.0.1
222
+ ## @effect/platform-node@4.1.0
223
223
 
224
224
  License: MIT
225
225
 
@@ -247,7 +247,7 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
247
247
  SOFTWARE.
248
248
  ```
249
249
 
250
- ## @effect/platform-node-shared@4.0.1
250
+ ## @effect/platform-node-shared@4.1.0
251
251
 
252
252
  License: MIT
253
253
 
@@ -275,7 +275,7 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
275
275
  SOFTWARE.
276
276
  ```
277
277
 
278
- ## @ioredis/commands@1.10.0
278
+ ## @ioredis/commands@2.0.0
279
279
 
280
280
  License: MIT
281
281
 
@@ -1552,7 +1552,7 @@ Apache License
1552
1552
  limitations under the License.
1553
1553
  ```
1554
1554
 
1555
- ## @opentelemetry/context-async-hooks@2.11.0
1555
+ ## @opentelemetry/context-async-hooks@2.12.0
1556
1556
 
1557
1557
  License: Apache-2.0
1558
1558
 
@@ -1760,7 +1760,7 @@ Apache License
1760
1760
  limitations under the License.
1761
1761
  ```
1762
1762
 
1763
- ## @opentelemetry/core@2.10.0
1763
+ ## @opentelemetry/core@2.12.0
1764
1764
 
1765
1765
  License: Apache-2.0
1766
1766
 
@@ -3008,6 +3008,214 @@ Apache License
3008
3008
  limitations under the License.
3009
3009
  ```
3010
3010
 
3011
+ ## @opentelemetry/resources@2.12.0
3012
+
3013
+ License: Apache-2.0
3014
+
3015
+ ```
3016
+ Apache License
3017
+ Version 2.0, January 2004
3018
+ http://www.apache.org/licenses/
3019
+
3020
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
3021
+
3022
+ 1. Definitions.
3023
+
3024
+ "License" shall mean the terms and conditions for use, reproduction,
3025
+ and distribution as defined by Sections 1 through 9 of this document.
3026
+
3027
+ "Licensor" shall mean the copyright owner or entity authorized by
3028
+ the copyright owner that is granting the License.
3029
+
3030
+ "Legal Entity" shall mean the union of the acting entity and all
3031
+ other entities that control, are controlled by, or are under common
3032
+ control with that entity. For the purposes of this definition,
3033
+ "control" means (i) the power, direct or indirect, to cause the
3034
+ direction or management of such entity, whether by contract or
3035
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
3036
+ outstanding shares, or (iii) beneficial ownership of such entity.
3037
+
3038
+ "You" (or "Your") shall mean an individual or Legal Entity
3039
+ exercising permissions granted by this License.
3040
+
3041
+ "Source" form shall mean the preferred form for making modifications,
3042
+ including but not limited to software source code, documentation
3043
+ source, and configuration files.
3044
+
3045
+ "Object" form shall mean any form resulting from mechanical
3046
+ transformation or translation of a Source form, including but
3047
+ not limited to compiled object code, generated documentation,
3048
+ and conversions to other media types.
3049
+
3050
+ "Work" shall mean the work of authorship, whether in Source or
3051
+ Object form, made available under the License, as indicated by a
3052
+ copyright notice that is included in or attached to the work
3053
+ (an example is provided in the Appendix below).
3054
+
3055
+ "Derivative Works" shall mean any work, whether in Source or Object
3056
+ form, that is based on (or derived from) the Work and for which the
3057
+ editorial revisions, annotations, elaborations, or other modifications
3058
+ represent, as a whole, an original work of authorship. For the purposes
3059
+ of this License, Derivative Works shall not include works that remain
3060
+ separable from, or merely link (or bind by name) to the interfaces of,
3061
+ the Work and Derivative Works thereof.
3062
+
3063
+ "Contribution" shall mean any work of authorship, including
3064
+ the original version of the Work and any modifications or additions
3065
+ to that Work or Derivative Works thereof, that is intentionally
3066
+ submitted to Licensor for inclusion in the Work by the copyright owner
3067
+ or by an individual or Legal Entity authorized to submit on behalf of
3068
+ the copyright owner. For the purposes of this definition, "submitted"
3069
+ means any form of electronic, verbal, or written communication sent
3070
+ to the Licensor or its representatives, including but not limited to
3071
+ communication on electronic mailing lists, source code control systems,
3072
+ and issue tracking systems that are managed by, or on behalf of, the
3073
+ Licensor for the purpose of discussing and improving the Work, but
3074
+ excluding communication that is conspicuously marked or otherwise
3075
+ designated in writing by the copyright owner as "Not a Contribution."
3076
+
3077
+ "Contributor" shall mean Licensor and any individual or Legal Entity
3078
+ on behalf of whom a Contribution has been received by Licensor and
3079
+ subsequently incorporated within the Work.
3080
+
3081
+ 2. Grant of Copyright License. Subject to the terms and conditions of
3082
+ this License, each Contributor hereby grants to You a perpetual,
3083
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
3084
+ copyright license to reproduce, prepare Derivative Works of,
3085
+ publicly display, publicly perform, sublicense, and distribute the
3086
+ Work and such Derivative Works in Source or Object form.
3087
+
3088
+ 3. Grant of Patent License. Subject to the terms and conditions of
3089
+ this License, each Contributor hereby grants to You a perpetual,
3090
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
3091
+ (except as stated in this section) patent license to make, have made,
3092
+ use, offer to sell, sell, import, and otherwise transfer the Work,
3093
+ where such license applies only to those patent claims licensable
3094
+ by such Contributor that are necessarily infringed by their
3095
+ Contribution(s) alone or by combination of their Contribution(s)
3096
+ with the Work to which such Contribution(s) was submitted. If You
3097
+ institute patent litigation against any entity (including a
3098
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
3099
+ or a Contribution incorporated within the Work constitutes direct
3100
+ or contributory patent infringement, then any patent licenses
3101
+ granted to You under this License for that Work shall terminate
3102
+ as of the date such litigation is filed.
3103
+
3104
+ 4. Redistribution. You may reproduce and distribute copies of the
3105
+ Work or Derivative Works thereof in any medium, with or without
3106
+ modifications, and in Source or Object form, provided that You
3107
+ meet the following conditions:
3108
+
3109
+ (a) You must give any other recipients of the Work or
3110
+ Derivative Works a copy of this License; and
3111
+
3112
+ (b) You must cause any modified files to carry prominent notices
3113
+ stating that You changed the files; and
3114
+
3115
+ (c) You must retain, in the Source form of any Derivative Works
3116
+ that You distribute, all copyright, patent, trademark, and
3117
+ attribution notices from the Source form of the Work,
3118
+ excluding those notices that do not pertain to any part of
3119
+ the Derivative Works; and
3120
+
3121
+ (d) If the Work includes a "NOTICE" text file as part of its
3122
+ distribution, then any Derivative Works that You distribute must
3123
+ include a readable copy of the attribution notices contained
3124
+ within such NOTICE file, excluding those notices that do not
3125
+ pertain to any part of the Derivative Works, in at least one
3126
+ of the following places: within a NOTICE text file distributed
3127
+ as part of the Derivative Works; within the Source form or
3128
+ documentation, if provided along with the Derivative Works; or,
3129
+ within a display generated by the Derivative Works, if and
3130
+ wherever such third-party notices normally appear. The contents
3131
+ of the NOTICE file are for informational purposes only and
3132
+ do not modify the License. You may add Your own attribution
3133
+ notices within Derivative Works that You distribute, alongside
3134
+ or as an addendum to the NOTICE text from the Work, provided
3135
+ that such additional attribution notices cannot be construed
3136
+ as modifying the License.
3137
+
3138
+ You may add Your own copyright statement to Your modifications and
3139
+ may provide additional or different license terms and conditions
3140
+ for use, reproduction, or distribution of Your modifications, or
3141
+ for any such Derivative Works as a whole, provided Your use,
3142
+ reproduction, and distribution of the Work otherwise complies with
3143
+ the conditions stated in this License.
3144
+
3145
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
3146
+ any Contribution intentionally submitted for inclusion in the Work
3147
+ by You to the Licensor shall be under the terms and conditions of
3148
+ this License, without any additional terms or conditions.
3149
+ Notwithstanding the above, nothing herein shall supersede or modify
3150
+ the terms of any separate license agreement you may have executed
3151
+ with Licensor regarding such Contributions.
3152
+
3153
+ 6. Trademarks. This License does not grant permission to use the trade
3154
+ names, trademarks, service marks, or product names of the Licensor,
3155
+ except as required for reasonable and customary use in describing the
3156
+ origin of the Work and reproducing the content of the NOTICE file.
3157
+
3158
+ 7. Disclaimer of Warranty. Unless required by applicable law or
3159
+ agreed to in writing, Licensor provides the Work (and each
3160
+ Contributor provides its Contributions) on an "AS IS" BASIS,
3161
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
3162
+ implied, including, without limitation, any warranties or conditions
3163
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
3164
+ PARTICULAR PURPOSE. You are solely responsible for determining the
3165
+ appropriateness of using or redistributing the Work and assume any
3166
+ risks associated with Your exercise of permissions under this License.
3167
+
3168
+ 8. Limitation of Liability. In no event and under no legal theory,
3169
+ whether in tort (including negligence), contract, or otherwise,
3170
+ unless required by applicable law (such as deliberate and grossly
3171
+ negligent acts) or agreed to in writing, shall any Contributor be
3172
+ liable to You for damages, including any direct, indirect, special,
3173
+ incidental, or consequential damages of any character arising as a
3174
+ result of this License or out of the use or inability to use the
3175
+ Work (including but not limited to damages for loss of goodwill,
3176
+ work stoppage, computer failure or malfunction, or any and all
3177
+ other commercial damages or losses), even if such Contributor
3178
+ has been advised of the possibility of such damages.
3179
+
3180
+ 9. Accepting Warranty or Additional Liability. While redistributing
3181
+ the Work or Derivative Works thereof, You may choose to offer,
3182
+ and charge a fee for, acceptance of support, warranty, indemnity,
3183
+ or other liability obligations and/or rights consistent with this
3184
+ License. However, in accepting such obligations, You may act only
3185
+ on Your own behalf and on Your sole responsibility, not on behalf
3186
+ of any other Contributor, and only if You agree to indemnify,
3187
+ defend, and hold each Contributor harmless for any liability
3188
+ incurred by, or claims asserted against, such Contributor by reason
3189
+ of your accepting any such warranty or additional liability.
3190
+
3191
+ END OF TERMS AND CONDITIONS
3192
+
3193
+ APPENDIX: How to apply the Apache License to your work.
3194
+
3195
+ To apply the Apache License to your work, attach the following
3196
+ boilerplate notice, with the fields enclosed by brackets "[]"
3197
+ replaced with your own identifying information. (Don't include
3198
+ the brackets!) The text should be enclosed in the appropriate
3199
+ comment syntax for the file format. We also recommend that a
3200
+ file or class name and description of purpose be included on the
3201
+ same "printed page" as the copyright notice for easier
3202
+ identification within third-party archives.
3203
+
3204
+ Copyright [yyyy] [name of copyright owner]
3205
+
3206
+ Licensed under the Apache License, Version 2.0 (the "License");
3207
+ you may not use this file except in compliance with the License.
3208
+ You may obtain a copy of the License at
3209
+
3210
+ http://www.apache.org/licenses/LICENSE-2.0
3211
+
3212
+ Unless required by applicable law or agreed to in writing, software
3213
+ distributed under the License is distributed on an "AS IS" BASIS,
3214
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
3215
+ See the License for the specific language governing permissions and
3216
+ limitations under the License.
3217
+ ```
3218
+
3011
3219
  ## @opentelemetry/sdk-logs@0.222.0
3012
3220
 
3013
3221
  License: Apache-2.0
@@ -3216,7 +3424,215 @@ Apache License
3216
3424
  limitations under the License.
3217
3425
  ```
3218
3426
 
3219
- ## @opentelemetry/sdk-metrics@2.11.0
3427
+ ## @opentelemetry/sdk-metrics@2.11.0
3428
+
3429
+ License: Apache-2.0
3430
+
3431
+ ```
3432
+ Apache License
3433
+ Version 2.0, January 2004
3434
+ http://www.apache.org/licenses/
3435
+
3436
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
3437
+
3438
+ 1. Definitions.
3439
+
3440
+ "License" shall mean the terms and conditions for use, reproduction,
3441
+ and distribution as defined by Sections 1 through 9 of this document.
3442
+
3443
+ "Licensor" shall mean the copyright owner or entity authorized by
3444
+ the copyright owner that is granting the License.
3445
+
3446
+ "Legal Entity" shall mean the union of the acting entity and all
3447
+ other entities that control, are controlled by, or are under common
3448
+ control with that entity. For the purposes of this definition,
3449
+ "control" means (i) the power, direct or indirect, to cause the
3450
+ direction or management of such entity, whether by contract or
3451
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
3452
+ outstanding shares, or (iii) beneficial ownership of such entity.
3453
+
3454
+ "You" (or "Your") shall mean an individual or Legal Entity
3455
+ exercising permissions granted by this License.
3456
+
3457
+ "Source" form shall mean the preferred form for making modifications,
3458
+ including but not limited to software source code, documentation
3459
+ source, and configuration files.
3460
+
3461
+ "Object" form shall mean any form resulting from mechanical
3462
+ transformation or translation of a Source form, including but
3463
+ not limited to compiled object code, generated documentation,
3464
+ and conversions to other media types.
3465
+
3466
+ "Work" shall mean the work of authorship, whether in Source or
3467
+ Object form, made available under the License, as indicated by a
3468
+ copyright notice that is included in or attached to the work
3469
+ (an example is provided in the Appendix below).
3470
+
3471
+ "Derivative Works" shall mean any work, whether in Source or Object
3472
+ form, that is based on (or derived from) the Work and for which the
3473
+ editorial revisions, annotations, elaborations, or other modifications
3474
+ represent, as a whole, an original work of authorship. For the purposes
3475
+ of this License, Derivative Works shall not include works that remain
3476
+ separable from, or merely link (or bind by name) to the interfaces of,
3477
+ the Work and Derivative Works thereof.
3478
+
3479
+ "Contribution" shall mean any work of authorship, including
3480
+ the original version of the Work and any modifications or additions
3481
+ to that Work or Derivative Works thereof, that is intentionally
3482
+ submitted to Licensor for inclusion in the Work by the copyright owner
3483
+ or by an individual or Legal Entity authorized to submit on behalf of
3484
+ the copyright owner. For the purposes of this definition, "submitted"
3485
+ means any form of electronic, verbal, or written communication sent
3486
+ to the Licensor or its representatives, including but not limited to
3487
+ communication on electronic mailing lists, source code control systems,
3488
+ and issue tracking systems that are managed by, or on behalf of, the
3489
+ Licensor for the purpose of discussing and improving the Work, but
3490
+ excluding communication that is conspicuously marked or otherwise
3491
+ designated in writing by the copyright owner as "Not a Contribution."
3492
+
3493
+ "Contributor" shall mean Licensor and any individual or Legal Entity
3494
+ on behalf of whom a Contribution has been received by Licensor and
3495
+ subsequently incorporated within the Work.
3496
+
3497
+ 2. Grant of Copyright License. Subject to the terms and conditions of
3498
+ this License, each Contributor hereby grants to You a perpetual,
3499
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
3500
+ copyright license to reproduce, prepare Derivative Works of,
3501
+ publicly display, publicly perform, sublicense, and distribute the
3502
+ Work and such Derivative Works in Source or Object form.
3503
+
3504
+ 3. Grant of Patent License. Subject to the terms and conditions of
3505
+ this License, each Contributor hereby grants to You a perpetual,
3506
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
3507
+ (except as stated in this section) patent license to make, have made,
3508
+ use, offer to sell, sell, import, and otherwise transfer the Work,
3509
+ where such license applies only to those patent claims licensable
3510
+ by such Contributor that are necessarily infringed by their
3511
+ Contribution(s) alone or by combination of their Contribution(s)
3512
+ with the Work to which such Contribution(s) was submitted. If You
3513
+ institute patent litigation against any entity (including a
3514
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
3515
+ or a Contribution incorporated within the Work constitutes direct
3516
+ or contributory patent infringement, then any patent licenses
3517
+ granted to You under this License for that Work shall terminate
3518
+ as of the date such litigation is filed.
3519
+
3520
+ 4. Redistribution. You may reproduce and distribute copies of the
3521
+ Work or Derivative Works thereof in any medium, with or without
3522
+ modifications, and in Source or Object form, provided that You
3523
+ meet the following conditions:
3524
+
3525
+ (a) You must give any other recipients of the Work or
3526
+ Derivative Works a copy of this License; and
3527
+
3528
+ (b) You must cause any modified files to carry prominent notices
3529
+ stating that You changed the files; and
3530
+
3531
+ (c) You must retain, in the Source form of any Derivative Works
3532
+ that You distribute, all copyright, patent, trademark, and
3533
+ attribution notices from the Source form of the Work,
3534
+ excluding those notices that do not pertain to any part of
3535
+ the Derivative Works; and
3536
+
3537
+ (d) If the Work includes a "NOTICE" text file as part of its
3538
+ distribution, then any Derivative Works that You distribute must
3539
+ include a readable copy of the attribution notices contained
3540
+ within such NOTICE file, excluding those notices that do not
3541
+ pertain to any part of the Derivative Works, in at least one
3542
+ of the following places: within a NOTICE text file distributed
3543
+ as part of the Derivative Works; within the Source form or
3544
+ documentation, if provided along with the Derivative Works; or,
3545
+ within a display generated by the Derivative Works, if and
3546
+ wherever such third-party notices normally appear. The contents
3547
+ of the NOTICE file are for informational purposes only and
3548
+ do not modify the License. You may add Your own attribution
3549
+ notices within Derivative Works that You distribute, alongside
3550
+ or as an addendum to the NOTICE text from the Work, provided
3551
+ that such additional attribution notices cannot be construed
3552
+ as modifying the License.
3553
+
3554
+ You may add Your own copyright statement to Your modifications and
3555
+ may provide additional or different license terms and conditions
3556
+ for use, reproduction, or distribution of Your modifications, or
3557
+ for any such Derivative Works as a whole, provided Your use,
3558
+ reproduction, and distribution of the Work otherwise complies with
3559
+ the conditions stated in this License.
3560
+
3561
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
3562
+ any Contribution intentionally submitted for inclusion in the Work
3563
+ by You to the Licensor shall be under the terms and conditions of
3564
+ this License, without any additional terms or conditions.
3565
+ Notwithstanding the above, nothing herein shall supersede or modify
3566
+ the terms of any separate license agreement you may have executed
3567
+ with Licensor regarding such Contributions.
3568
+
3569
+ 6. Trademarks. This License does not grant permission to use the trade
3570
+ names, trademarks, service marks, or product names of the Licensor,
3571
+ except as required for reasonable and customary use in describing the
3572
+ origin of the Work and reproducing the content of the NOTICE file.
3573
+
3574
+ 7. Disclaimer of Warranty. Unless required by applicable law or
3575
+ agreed to in writing, Licensor provides the Work (and each
3576
+ Contributor provides its Contributions) on an "AS IS" BASIS,
3577
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
3578
+ implied, including, without limitation, any warranties or conditions
3579
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
3580
+ PARTICULAR PURPOSE. You are solely responsible for determining the
3581
+ appropriateness of using or redistributing the Work and assume any
3582
+ risks associated with Your exercise of permissions under this License.
3583
+
3584
+ 8. Limitation of Liability. In no event and under no legal theory,
3585
+ whether in tort (including negligence), contract, or otherwise,
3586
+ unless required by applicable law (such as deliberate and grossly
3587
+ negligent acts) or agreed to in writing, shall any Contributor be
3588
+ liable to You for damages, including any direct, indirect, special,
3589
+ incidental, or consequential damages of any character arising as a
3590
+ result of this License or out of the use or inability to use the
3591
+ Work (including but not limited to damages for loss of goodwill,
3592
+ work stoppage, computer failure or malfunction, or any and all
3593
+ other commercial damages or losses), even if such Contributor
3594
+ has been advised of the possibility of such damages.
3595
+
3596
+ 9. Accepting Warranty or Additional Liability. While redistributing
3597
+ the Work or Derivative Works thereof, You may choose to offer,
3598
+ and charge a fee for, acceptance of support, warranty, indemnity,
3599
+ or other liability obligations and/or rights consistent with this
3600
+ License. However, in accepting such obligations, You may act only
3601
+ on Your own behalf and on Your sole responsibility, not on behalf
3602
+ of any other Contributor, and only if You agree to indemnify,
3603
+ defend, and hold each Contributor harmless for any liability
3604
+ incurred by, or claims asserted against, such Contributor by reason
3605
+ of your accepting any such warranty or additional liability.
3606
+
3607
+ END OF TERMS AND CONDITIONS
3608
+
3609
+ APPENDIX: How to apply the Apache License to your work.
3610
+
3611
+ To apply the Apache License to your work, attach the following
3612
+ boilerplate notice, with the fields enclosed by brackets "[]"
3613
+ replaced with your own identifying information. (Don't include
3614
+ the brackets!) The text should be enclosed in the appropriate
3615
+ comment syntax for the file format. We also recommend that a
3616
+ file or class name and description of purpose be included on the
3617
+ same "printed page" as the copyright notice for easier
3618
+ identification within third-party archives.
3619
+
3620
+ Copyright [yyyy] [name of copyright owner]
3621
+
3622
+ Licensed under the Apache License, Version 2.0 (the "License");
3623
+ you may not use this file except in compliance with the License.
3624
+ You may obtain a copy of the License at
3625
+
3626
+ http://www.apache.org/licenses/LICENSE-2.0
3627
+
3628
+ Unless required by applicable law or agreed to in writing, software
3629
+ distributed under the License is distributed on an "AS IS" BASIS,
3630
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
3631
+ See the License for the specific language governing permissions and
3632
+ limitations under the License.
3633
+ ```
3634
+
3635
+ ## @opentelemetry/sdk-metrics@2.12.0
3220
3636
 
3221
3637
  License: Apache-2.0
3222
3638
 
@@ -3632,7 +4048,215 @@ Apache License
3632
4048
  limitations under the License.
3633
4049
  ```
3634
4050
 
3635
- ## @opentelemetry/sdk-trace-base@2.11.0
4051
+ ## @opentelemetry/sdk-trace@2.12.0
4052
+
4053
+ License: Apache-2.0
4054
+
4055
+ ```
4056
+ Apache License
4057
+ Version 2.0, January 2004
4058
+ http://www.apache.org/licenses/
4059
+
4060
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
4061
+
4062
+ 1. Definitions.
4063
+
4064
+ "License" shall mean the terms and conditions for use, reproduction,
4065
+ and distribution as defined by Sections 1 through 9 of this document.
4066
+
4067
+ "Licensor" shall mean the copyright owner or entity authorized by
4068
+ the copyright owner that is granting the License.
4069
+
4070
+ "Legal Entity" shall mean the union of the acting entity and all
4071
+ other entities that control, are controlled by, or are under common
4072
+ control with that entity. For the purposes of this definition,
4073
+ "control" means (i) the power, direct or indirect, to cause the
4074
+ direction or management of such entity, whether by contract or
4075
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
4076
+ outstanding shares, or (iii) beneficial ownership of such entity.
4077
+
4078
+ "You" (or "Your") shall mean an individual or Legal Entity
4079
+ exercising permissions granted by this License.
4080
+
4081
+ "Source" form shall mean the preferred form for making modifications,
4082
+ including but not limited to software source code, documentation
4083
+ source, and configuration files.
4084
+
4085
+ "Object" form shall mean any form resulting from mechanical
4086
+ transformation or translation of a Source form, including but
4087
+ not limited to compiled object code, generated documentation,
4088
+ and conversions to other media types.
4089
+
4090
+ "Work" shall mean the work of authorship, whether in Source or
4091
+ Object form, made available under the License, as indicated by a
4092
+ copyright notice that is included in or attached to the work
4093
+ (an example is provided in the Appendix below).
4094
+
4095
+ "Derivative Works" shall mean any work, whether in Source or Object
4096
+ form, that is based on (or derived from) the Work and for which the
4097
+ editorial revisions, annotations, elaborations, or other modifications
4098
+ represent, as a whole, an original work of authorship. For the purposes
4099
+ of this License, Derivative Works shall not include works that remain
4100
+ separable from, or merely link (or bind by name) to the interfaces of,
4101
+ the Work and Derivative Works thereof.
4102
+
4103
+ "Contribution" shall mean any work of authorship, including
4104
+ the original version of the Work and any modifications or additions
4105
+ to that Work or Derivative Works thereof, that is intentionally
4106
+ submitted to Licensor for inclusion in the Work by the copyright owner
4107
+ or by an individual or Legal Entity authorized to submit on behalf of
4108
+ the copyright owner. For the purposes of this definition, "submitted"
4109
+ means any form of electronic, verbal, or written communication sent
4110
+ to the Licensor or its representatives, including but not limited to
4111
+ communication on electronic mailing lists, source code control systems,
4112
+ and issue tracking systems that are managed by, or on behalf of, the
4113
+ Licensor for the purpose of discussing and improving the Work, but
4114
+ excluding communication that is conspicuously marked or otherwise
4115
+ designated in writing by the copyright owner as "Not a Contribution."
4116
+
4117
+ "Contributor" shall mean Licensor and any individual or Legal Entity
4118
+ on behalf of whom a Contribution has been received by Licensor and
4119
+ subsequently incorporated within the Work.
4120
+
4121
+ 2. Grant of Copyright License. Subject to the terms and conditions of
4122
+ this License, each Contributor hereby grants to You a perpetual,
4123
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
4124
+ copyright license to reproduce, prepare Derivative Works of,
4125
+ publicly display, publicly perform, sublicense, and distribute the
4126
+ Work and such Derivative Works in Source or Object form.
4127
+
4128
+ 3. Grant of Patent License. Subject to the terms and conditions of
4129
+ this License, each Contributor hereby grants to You a perpetual,
4130
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
4131
+ (except as stated in this section) patent license to make, have made,
4132
+ use, offer to sell, sell, import, and otherwise transfer the Work,
4133
+ where such license applies only to those patent claims licensable
4134
+ by such Contributor that are necessarily infringed by their
4135
+ Contribution(s) alone or by combination of their Contribution(s)
4136
+ with the Work to which such Contribution(s) was submitted. If You
4137
+ institute patent litigation against any entity (including a
4138
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
4139
+ or a Contribution incorporated within the Work constitutes direct
4140
+ or contributory patent infringement, then any patent licenses
4141
+ granted to You under this License for that Work shall terminate
4142
+ as of the date such litigation is filed.
4143
+
4144
+ 4. Redistribution. You may reproduce and distribute copies of the
4145
+ Work or Derivative Works thereof in any medium, with or without
4146
+ modifications, and in Source or Object form, provided that You
4147
+ meet the following conditions:
4148
+
4149
+ (a) You must give any other recipients of the Work or
4150
+ Derivative Works a copy of this License; and
4151
+
4152
+ (b) You must cause any modified files to carry prominent notices
4153
+ stating that You changed the files; and
4154
+
4155
+ (c) You must retain, in the Source form of any Derivative Works
4156
+ that You distribute, all copyright, patent, trademark, and
4157
+ attribution notices from the Source form of the Work,
4158
+ excluding those notices that do not pertain to any part of
4159
+ the Derivative Works; and
4160
+
4161
+ (d) If the Work includes a "NOTICE" text file as part of its
4162
+ distribution, then any Derivative Works that You distribute must
4163
+ include a readable copy of the attribution notices contained
4164
+ within such NOTICE file, excluding those notices that do not
4165
+ pertain to any part of the Derivative Works, in at least one
4166
+ of the following places: within a NOTICE text file distributed
4167
+ as part of the Derivative Works; within the Source form or
4168
+ documentation, if provided along with the Derivative Works; or,
4169
+ within a display generated by the Derivative Works, if and
4170
+ wherever such third-party notices normally appear. The contents
4171
+ of the NOTICE file are for informational purposes only and
4172
+ do not modify the License. You may add Your own attribution
4173
+ notices within Derivative Works that You distribute, alongside
4174
+ or as an addendum to the NOTICE text from the Work, provided
4175
+ that such additional attribution notices cannot be construed
4176
+ as modifying the License.
4177
+
4178
+ You may add Your own copyright statement to Your modifications and
4179
+ may provide additional or different license terms and conditions
4180
+ for use, reproduction, or distribution of Your modifications, or
4181
+ for any such Derivative Works as a whole, provided Your use,
4182
+ reproduction, and distribution of the Work otherwise complies with
4183
+ the conditions stated in this License.
4184
+
4185
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
4186
+ any Contribution intentionally submitted for inclusion in the Work
4187
+ by You to the Licensor shall be under the terms and conditions of
4188
+ this License, without any additional terms or conditions.
4189
+ Notwithstanding the above, nothing herein shall supersede or modify
4190
+ the terms of any separate license agreement you may have executed
4191
+ with Licensor regarding such Contributions.
4192
+
4193
+ 6. Trademarks. This License does not grant permission to use the trade
4194
+ names, trademarks, service marks, or product names of the Licensor,
4195
+ except as required for reasonable and customary use in describing the
4196
+ origin of the Work and reproducing the content of the NOTICE file.
4197
+
4198
+ 7. Disclaimer of Warranty. Unless required by applicable law or
4199
+ agreed to in writing, Licensor provides the Work (and each
4200
+ Contributor provides its Contributions) on an "AS IS" BASIS,
4201
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
4202
+ implied, including, without limitation, any warranties or conditions
4203
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
4204
+ PARTICULAR PURPOSE. You are solely responsible for determining the
4205
+ appropriateness of using or redistributing the Work and assume any
4206
+ risks associated with Your exercise of permissions under this License.
4207
+
4208
+ 8. Limitation of Liability. In no event and under no legal theory,
4209
+ whether in tort (including negligence), contract, or otherwise,
4210
+ unless required by applicable law (such as deliberate and grossly
4211
+ negligent acts) or agreed to in writing, shall any Contributor be
4212
+ liable to You for damages, including any direct, indirect, special,
4213
+ incidental, or consequential damages of any character arising as a
4214
+ result of this License or out of the use or inability to use the
4215
+ Work (including but not limited to damages for loss of goodwill,
4216
+ work stoppage, computer failure or malfunction, or any and all
4217
+ other commercial damages or losses), even if such Contributor
4218
+ has been advised of the possibility of such damages.
4219
+
4220
+ 9. Accepting Warranty or Additional Liability. While redistributing
4221
+ the Work or Derivative Works thereof, You may choose to offer,
4222
+ and charge a fee for, acceptance of support, warranty, indemnity,
4223
+ or other liability obligations and/or rights consistent with this
4224
+ License. However, in accepting such obligations, You may act only
4225
+ on Your own behalf and on Your sole responsibility, not on behalf
4226
+ of any other Contributor, and only if You agree to indemnify,
4227
+ defend, and hold each Contributor harmless for any liability
4228
+ incurred by, or claims asserted against, such Contributor by reason
4229
+ of your accepting any such warranty or additional liability.
4230
+
4231
+ END OF TERMS AND CONDITIONS
4232
+
4233
+ APPENDIX: How to apply the Apache License to your work.
4234
+
4235
+ To apply the Apache License to your work, attach the following
4236
+ boilerplate notice, with the fields enclosed by brackets "[]"
4237
+ replaced with your own identifying information. (Don't include
4238
+ the brackets!) The text should be enclosed in the appropriate
4239
+ comment syntax for the file format. We also recommend that a
4240
+ file or class name and description of purpose be included on the
4241
+ same "printed page" as the copyright notice for easier
4242
+ identification within third-party archives.
4243
+
4244
+ Copyright [yyyy] [name of copyright owner]
4245
+
4246
+ Licensed under the Apache License, Version 2.0 (the "License");
4247
+ you may not use this file except in compliance with the License.
4248
+ You may obtain a copy of the License at
4249
+
4250
+ http://www.apache.org/licenses/LICENSE-2.0
4251
+
4252
+ Unless required by applicable law or agreed to in writing, software
4253
+ distributed under the License is distributed on an "AS IS" BASIS,
4254
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
4255
+ See the License for the specific language governing permissions and
4256
+ limitations under the License.
4257
+ ```
4258
+
4259
+ ## @opentelemetry/sdk-trace-base@2.12.0
3636
4260
 
3637
4261
  License: Apache-2.0
3638
4262
 
@@ -3840,7 +4464,7 @@ Apache License
3840
4464
  limitations under the License.
3841
4465
  ```
3842
4466
 
3843
- ## @opentelemetry/sdk-trace-node@2.11.0
4467
+ ## @opentelemetry/sdk-trace-node@2.12.0
3844
4468
 
3845
4469
  License: Apache-2.0
3846
4470
 
@@ -4048,7 +4672,7 @@ Apache License
4048
4672
  limitations under the License.
4049
4673
  ```
4050
4674
 
4051
- ## @opentelemetry/semantic-conventions@1.43.0
4675
+ ## @opentelemetry/semantic-conventions@1.44.0
4052
4676
 
4053
4677
  License: Apache-2.0
4054
4678
 
@@ -4256,7 +4880,7 @@ Apache License
4256
4880
  limitations under the License.
4257
4881
  ```
4258
4882
 
4259
- ## @types/node@26.4.1
4883
+ ## @types/node@26.6.6
4260
4884
 
4261
4885
  License: MIT
4262
4886
 
@@ -4284,7 +4908,7 @@ MIT License
4284
4908
  SOFTWARE
4285
4909
  ```
4286
4910
 
4287
- ## @types/ws@8.18.1
4911
+ ## @types/ws@8.18.2
4288
4912
 
4289
4913
  License: MIT
4290
4914
 
@@ -4312,7 +4936,7 @@ MIT License
4312
4936
  SOFTWARE
4313
4937
  ```
4314
4938
 
4315
- ## @upstash/redis@1.38.4
4939
+ ## @upstash/redis@1.40.0
4316
4940
 
4317
4941
  License: MIT
4318
4942
 
@@ -4594,7 +5218,7 @@ Apache License
4594
5218
  limitations under the License.
4595
5219
  ```
4596
5220
 
4597
- ## ioredis@5.11.1
5221
+ ## ioredis@6.0.0
4598
5222
 
4599
5223
  License: MIT
4600
5224
 
@@ -4650,7 +5274,7 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
4650
5274
  SOFTWARE.
4651
5275
  ```
4652
5276
 
4653
- ## jose@6.2.12
5277
+ ## jose@6.2.13
4654
5278
 
4655
5279
  License: MIT
4656
5280
 
@@ -4678,7 +5302,7 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
4678
5302
  SOFTWARE.
4679
5303
  ```
4680
5304
 
4681
- ## lib0@0.2.117
5305
+ ## lib0@0.2.119
4682
5306
 
4683
5307
  License: MIT
4684
5308
 
@@ -4762,34 +5386,6 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
4762
5386
  SOFTWARE.
4763
5387
  ```
4764
5388
 
4765
- ## redis-parser@3.0.0
4766
-
4767
- License: MIT
4768
-
4769
- ```
4770
- The MIT License (MIT)
4771
-
4772
- Copyright (c) 2015 NodeRedis
4773
-
4774
- Permission is hereby granted, free of charge, to any person obtaining a copy
4775
- of this software and associated documentation files (the "Software"), to deal
4776
- in the Software without restriction, including without limitation the rights
4777
- to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
4778
- copies of the Software, and to permit persons to whom the Software is
4779
- furnished to do so, subject to the following conditions:
4780
-
4781
- The above copyright notice and this permission notice shall be included in all
4782
- copies or substantial portions of the Software.
4783
-
4784
- THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
4785
- IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
4786
- FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
4787
- AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
4788
- LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
4789
- OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
4790
- SOFTWARE.
4791
- ```
4792
-
4793
5389
  ## standard-as-callback@2.1.0
4794
5390
 
4795
5391
  License: MIT
@@ -4934,7 +5530,7 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
4934
5530
  SOFTWARE.
4935
5531
  ```
4936
5532
 
4937
- ## undici-types@8.3.0
5533
+ ## undici-types@8.9.0
4938
5534
 
4939
5535
  License: MIT
4940
5536
 
@@ -4962,7 +5558,7 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
4962
5558
  SOFTWARE.
4963
5559
  ```
4964
5560
 
4965
- ## ws@8.21.0
5561
+ ## ws@8.22.0
4966
5562
 
4967
5563
  License: MIT
4968
5564
 
@@ -5017,7 +5613,7 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
5017
5613
  SOFTWARE.
5018
5614
  ```
5019
5615
 
5020
- ## yjs@13.6.32
5616
+ ## yjs@13.6.33
5021
5617
 
5022
5618
  License: MIT
5023
5619
 
package/dist/index.js CHANGED
@@ -1,7 +1,7 @@
1
1
  import { EVENTS_TABLE_DDL as e, MIRROR_TABLE_DDL as t, assertIdentifier as n, buildClickhouseSink as r, closeClickhouseState as i, makeEventBatcher as a } from "./sink.js";
2
2
  import { createClient as o } from "@clickhouse/client";
3
3
  import { Effect as s } from "effect";
4
- //#region src/index.ts
4
+ // src/index.ts
5
5
  var c = 20, l = 5e3, u = (u) => {
6
6
  let d = (u.mirrorTables ?? []).map((e) => n(e, "mirror table")), f = {
7
7
  client: null,
@@ -55,5 +55,4 @@ var c = 20, l = 5e3, u = (u) => {
55
55
  }).pipe(s.ensuring(i(f)))
56
56
  };
57
57
  };
58
- //#endregion
59
58
  export { e as EVENTS_TABLE_DDL, t as MIRROR_TABLE_DDL, u as clickhouseAnalytics };
package/dist/sink.js CHANGED
@@ -1,7 +1,7 @@
1
1
  import { Effect as e } from "effect";
2
2
  import { createLogger as t } from "@voltro/logger";
3
3
  import { AnalyticsError as n } from "@voltro/runtime";
4
- //#region src/sink.ts
4
+ // src/sink.ts
5
5
  var r = t({ scope: "@voltro/plugin-clickhouse" }), i = "clickhouse", a = (e) => `voltro_mirror_${e}`, o = (e, t) => `
6
6
  CREATE TABLE IF NOT EXISTS ${e}.${a(t)} (
7
7
  id String,
@@ -255,5 +255,4 @@ var r = t({ scope: "@voltro/plugin-clickhouse" }), i = "clickhouse", a = (e) =>
255
255
  ...n === void 0 ? {} : { mirror: n }
256
256
  };
257
257
  };
258
- //#endregion
259
258
  export { s as EVENTS_TABLE_DDL, o as MIRROR_TABLE_DDL, d as assertIdentifier, E as buildClickhouseSink, g as closeClickhouseState, v as makeEventBatcher, a as mirrorTableName };
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@voltro/plugin-clickhouse",
3
- "version": "0.87.0",
3
+ "version": "0.88.0",
4
4
  "description": "ClickHouse AnalyticsSink. Native HTTP ingest into a ClickHouse cluster — self-hosted OR ClickHouse Cloud. Production-grade OLAP for high-cardinality events with millisecond aggregate queries over billions of rows.",
5
5
  "keywords": [
6
6
  "voltro",
@@ -33,12 +33,12 @@
33
33
  "node": ">=24.0.0"
34
34
  },
35
35
  "dependencies": {
36
- "@clickhouse/client": "^1.23.1",
37
- "@voltro/logger": "0.87.0",
38
- "@voltro/runtime": "0.87.0"
36
+ "@clickhouse/client": "^1.24.1",
37
+ "@voltro/logger": "0.88.0",
38
+ "@voltro/runtime": "0.88.0"
39
39
  },
40
40
  "peerDependencies": {
41
- "effect": "4.0.1"
41
+ "effect": "4.1.0"
42
42
  },
43
43
  "publishConfig": {
44
44
  "access": "public"